I would like to hear your opinion about an approach, I would like to follow when creating new workflows in JSM.
Now I design workflows with all status needed, directly in the workflow. If anything is changing in the workflow (additional approval step, new status in the workflow needed) I need to adjust the whole workflow.
To reuse workflows for other use cases, compromises must be made to find the existing workflow to the new use case. (status names not fitting to the to do, missing steps/unnecessary steps)
So, I would like to design more flexible workflows, where often used sub sequences are outsourced to separate workflows. You can imagine it like modules attached together as needed.
We often need approval status in different shapes. Therefore, I have thought about this part more in depth.
My idea is to separate approvals and the working workflows into two different issues.
My idea consists of 3 parts that needs to be put together.
The customer creates a new issue. Because of the request type of the issue is identified as issue which needs 2 approvals.
After creating the issue, the status “approval needed” is reached and triggers the creation of the approval workflow. Within this workflow, it’s determined how many approvers are needed for this setup. The approvals are handled and if approved, reported back to the original issue.
After the approval the “To do” workflow will automatically transit out of the approval status and can be processed by the responsible.
With this approach I hope to get a more flexible setup, where changes on an approval setup don’t lead to a rework of a whole process. Additionally, I promise myself to get a workflow toolbox, from which I can select modules to fit to new use cases
Has anybody realized a similar setup yet and can point me to some points to be aware of?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events