Feature Requests

Add: Trigger Logic to Workflows Example: When an Action Card meets X criteria, in this case it would be when the existing card has a title of XYZ (or title contains XYZ), add a label.

In Workflows, it would be great to have the trigger "Ready to work on" which is when a dependency is completed the successive action will be "Ready to work on" an In-app notification is sent, but to have this as a trigger in Workflows will be incredibly useful. Examples such as send an email, reassign action, etc.

Currently, all workflow buttons everyone can see. However, it creates clutter because most Workflow buttons are supposed to be Private and then only some Client needs. They shouldn't be able to click the button to send themselves an email. That is my role.

There is too much information, could you make an option to choose which part of the data we include in the email? If [Action Title] is [1,2,3,] then we can select [1,2] only for the emails If [Created By] is [First Name, Last Name] we can select [First Name]

To highlight important information.

Currently, workflows can run on actions or actions and subactions — but not subactions only. Please add an option to trigger workflows only for subactions (any action below top-level action).

If newly added projects would auto populate into portfolio view, and then if we could separate out by our own priority to keep what we need to view (for example, for the upcoming week or two) towards the top of the view, that would be great. Each week I seem to have to add everything (because the titles are abbreviated) and then go line by line to hide projects that no longer need to remain in my particular portfolio view.

Outlook is a much richer email client than Hive (no offensive). It would be great if Hive had an add-in for Outlook 365 that allow users to send an email action to Hive which would create a task in a Project (like most of the other PM base tools have). Thanks so much

Currently, if you try to personalize it, it shows up as the entire email address not just [First name].

We have an automation that runs on every form submission. The owner of that automation gets added to every form submission, flooding her inbox with updates and alerts. Having someone added as a follower for an automation should be optional, not required.