M
Maria Steger
K
Kevon Lightfoot
Hi Maria Steger/Maria Steger, we shared a similar request and ultimately created our own automation using Hive Automate to accomplish this. (Actions can only be adjusted by a select group of individually assigned unique ids, the user when it matches the created by, and within a specific project.) Please let me know if your organization uses Hive Automate and would like the workflow to be shared.
M
Maria Steger
Hello Kevon Lightfoot, thank you so much for sharing your workaround. Yes, we would be very interested in seeing your workflow.
K
Kevon Lightfoot
Maria Steger Sorry for the delay here.
We use updated actions, with the status as the Trigger.
- This recipe is only triggered when the modifier isn't the/an Assignee.
- Fetch the full details of the Action. It'll allow you to compare properties more granularly. It isn't necessarily needed here but I've developed the habit of fetching full details for actions and users for any recipes that I use to assign actions, or email users.
- Confirm the assignee of the action that triggered the recipe is the person that modified it (attempted to update the status), or someone you've listed explicitly. In our organization, this list includes management/approvers. We want them to be allowed the freedom to revert/transition any action statuses they choose.
- If they match, perform the status change, else revert back to the Submitted status.