Feature Requests

Workflow buttons are helpful in moving action cards. It would be helpful if archived actions would be able to use them as well

In workflows, when automatically adding an individual subaction or subaction template, there is no way to set the statuses of these new subactions. The new subactions automatically inherit the status of the parent action. This is not solved by the workspace level status prompt when workflow automation is involved as a human is not being prompted. For items where the subaction must be set as 'unstarted' or 'unassigned' in order to be addressed operationally, there's no way to see these subactions as unstarted and assign them if the parent action is already in progress.

It would be great if a user can trigger an approval request if the action card gets completed or other triggers happen.

In the "Then Do This..." menu, I would like to see the ability to convert an Action to a Project. This would help as in a certain context Actions are treated as potential projects coming down the scoping and approval pipeline. Once they are approved I convert them to a project. Having the ability for them to automatically be converted to a project once their status is Approved (and then run further workflow functions) would be great.

The ability to add workflow buttons to a project AND action card with a specific label.

It would be great if a user can use fields like ({action_title}, {assignee_first_name}, {action_duedate}, etc) to populate an email sent using Workflows.

I organize table views by due date, with the next items due being at the top. Main tasks should have their due date default to whatever the next subtask's due date is. That way, my list of to-do items is still in order of whatever is literally due next, regardless if I'm comparing a main task versus a subtask of another main task. My current workaround is to manually copy the due date from a subtask into its main task's due date column. Now the whole main task snaps in order of when all my items are due. But I'll have to manually due this in per petuity.

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.

When making an automation button available in a project, it should be made available in all current and future child projects.