Feature Requests

It would be great if the time estimate on a task would automatically adjust based on the amount of work being done in the task. This could be accomplished by allowing the time estimate to be determined by a formula. The formula should be able to use any native datapoint found in Hive AND values from custom fields. We'd also need the ability to set up this formula per task type/task template, since the amount of time the task takes per unit of work changes from one task type to the next. The specific use case that would help me would look like this: "Time Estimate = [Custom Field Value] * 5" In this case, the custom field would be the "#of Properties" field. Another example: "Time Estimate = If/then Statement" "If [Custom Field] = Value A, Then [Time Estimate] = 4 Hours If [Custom Field] = Value B, Then [Time Estimate] = 6Hours" In this case, the custom field would be contract type. Another example: "Time Estimate =([Action Duration] * 5) / 60" These are examples of the kinds of variables that should be included in the formula options. This would be extremely helpful for routine tasks that don't require in-depth scoping for time estimates.

Recurring tickets do not currently allow users to duplicate approval rounds, only the ticket title/description/assignee(s). This means that users have to go in and manually add the approval rounds each time a ticket "recurs." For example, I have a weekly recurring ticket that requires two individuals to review/approve. Rather than simply carrying over the approval rounds, I have to manually go in each week to add the approval rounds.

Our admin often helps build summary views and all their tabs for people. We would like to be able to re-assign ownership of the view and the tabs to others after the admin has finished building them. That would allow the new owner that it was built for to rename, modify and even delete if desired. It is also very challenging to track down who "owns" a particular tab in a Summary View because the info does not seem to be listed anywhere.

When searching for a specific action card by the ID, multiple results may appear (especially when cards are linked or include cross references to others). It would save time in locating the required card if the Simple ID could be included in the displayed results.

Currently, the Action Card template modal does not allow you to select a status for your action card when applied and defaults to Unstarted. We would like the ability to add a status to actions and subactions in an Action Card template

Currently, Projects have unique Project ID but users are unable to search for projects using the ID if the project is archived.

It would be helpful to continue to be able to filter Archived Projects, just like we can filter Active projects. We would love to ability to filter to see what projects were completed for each client, or were completed by each of our staff members, etc.

It would be very useful if there was an option in setting up views to include archived projects. We lost a lot of open actions when a project was accidentally closed before it was reviewed properly.

When someone @ mentions you in a comment/annotation on a Hive proof, you get a Hive email notification, but there's zero context aside from the document title and who mentioned you. On the other hand, when someone @ mentions you in a comment on a card/subaction, the email notification includes the project title, the actual comment you were tagged in, previous comments for context and time stamps. This is crucial information to include in email notifications for proof mentions, too, so we know whether the comment is something we NEED to weigh in on, something that's just an FYI and not urgent, etc. Currently, it's simply another email bogging down the inbox requiring us to take another step (going into the proof ourselves) to determine all of the above — and that's not an efficient way to work.

Previous to the latest update, the search function was much easier to use and gave me the exact results I was looking for. It would be great to find a blend of what was rolled out and what worked so seamlessly in the last version.