Automatic assignment of approver when the status of a project is changed automatically
Hello,
I have created a specific status on the "Workflow" space called "Approval in progress" showing that an approval flow needs to be launched/finalized for any project. I have added in this specific status by default two assigned approvers.
In addition, I have created an automation rule stating that if all the sub-items of the project turn to completed and cancelled, then the status of the project changes automatically to "Approval in progress".
The issue here is that when I change manually the status of the project to "Approval in progress", then the approval flow is automatically assigned to the two assigned approvers, however when the status is automatically changed according to the automation rule, the approval flow is not launched nor assigned automatically to the two approvers.
My goal is the following one: when the status changes automatically to "Approval in progress", then an approval flow will automatically be launched with the two assigned approvers included.
Thank you in advance for your help! ☺️
I have experienced similar problems, it seems that automations cannot trigger other automations.
Would be good to see this change so that you can stack automations, either as default or by an option to link them together to create automation flows.
Hi Nawel DJELALIA, Zoe Jarrett, is not possible trigger an automation based on the result of another automation.
Have you setup approvers directly into Workflow status?
I have not, our approvers for a status change wouldn't always be going to the same person/people and the Approval set up in the workflow seems to require a specific assignee?
My use case for this was slightly different, what I would like to achieve is when the tester signs off the last bug in a bug list this marks the bug list ticket to Approved and then that change amends the status of the project to Approved to alert the Project owner.
Individually you can do either, but it requires a manual step to achieve both. So either the tester has to mark the main task as Approved (which is currently what we do) or someone would have to mark the Project to Approved.
I have had a few cases like this where we could cut out loads of small pieces of admin time if we could make automation flows, which would lead to significant time gains. This would also reduce cases of user error where people just forget to update parent tasks when they are open to a subtask.
Hi Zoe Jarrett
if I understand correctly, there are a series of "bugs" that are managed by different people, once the bug has been assigned, and then completed, whoever finished the work signals that the project owner will have to verify and approve the resolution of the bug. Correct?
If so, I would work this way:
1. I create a form that the Project Owner fills in every time a bug occurs
2. The bug is assigned to a specific person, who when he finishes the work, puts it in "to approve" status
3. When the status changes, an automation adds an approval to the author of the bug (i.e. whoever filled out the form)
Can this work for you?