A single issue can only be in one status at a time. If you need more than one status at a time, I generally recommend having more granular tasks to track multiple statuses.
You could set up a workflow using sub-tasks for approval. You might follow this scenario:
Great approach. I implemented this today and the sub tasks create automatically (as a post function), auto assign to the correct team and individual (using field ID instead of names), the right people get notified and the process uses automation to move the ticket through the transition steps as items get approved (or declined).
I had lost some sleep trying to think of a way to get this to work, so your idea was definitely an inspiration. It is frustrating that there's always 'an add on for that', and this proves that outside of the box thinking and sharing in forums makes us maximise the application and not the price!
I also created new sub task types (called 'approval') that has it's own screen scheme and workflow. It was worth the effort.
I've installed an add on too (freebit), to colour code the buttons (green is good, red is bad), which really helps.
I'm giving the stakeholders a demo later this week.....fingers crossed!
Hi @Nick Read It certainly was worth the effort, and after a few attempts at getting the logic right it wasn't as difficult as I initially thought.
The approach I took to make the Issue Type a new Issue Type so it was completely independent from other workflows, with it's own custom fields, but still a part of our main project.
I also created new sub task types within the project that had independant workflows associated with them.
When the main Issue Type is created, automation creates some initial sub tasks that are 'default'. The Summary, Description, Categorisation, assignment etc. all autofill.
During the workflow, once the issue type is 'ready' to move forward additional sub tasks are raised (the newly create sub tasks with independant workflows) and these have the approval stages.
The primary ticket cannot progress until the status of the sub tasks is in a certain stage, using the conditions logic.
I had used this approach before, but not to this extent - the approval piece from different departments was really critical to the workflow.
We end up with 5 different areas for approval - each works their own ticket at the own pace. It works like a dream.
I've not automated the primary ticket's automation to progress when all approvals are given, but that's a personal choice. It's sometimes a balance between keeping it simple, and staying 'engaged' with the process.
I did have another win during the build of this - I found a free add on that allowed me to colour the buttons, so approvers can clearly see their options "Approve" and "Reject". It's a simple win, but the feedback is really positive.
Good luck with your project!
does the project workflow requirement represent as an issue task for you to do?
You can do the following:
Finally, with workflow condition, you can make each transition button to appear to the relevant department.
Once a department click on the transition button, it will mark the checkbox (for you it means they sign on it), once they sign you can disappear the transition button, as they do not need to click again.
Hope that's what you wanted in the end.
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