We have put together a 34 step decommissioning workflow in JIRA. There are 2 steps that we need to enforce a delay to ensure there is sufficient time for feedback before skipping on to the next step.
For example, if step 5 is disable application front-end, the workflow should prevent anyone from advancing the issue to step 6 until at least 2 weeks has passed.
What is the best way to achieve this?
Very interesting question. And a 34-step workflow? I would love to learn more! You can email me at email@example.com
Here's my first idea on how to hack this. I'd use the JIRA Workflow Toolbox to store the current datetime into a custom variable during a transition:
Then I would add a condition from the same plug-in to the transition I wanted to delay:
Then you can compare the current datetime with the stored datetime. I agree that there may be other ways to do this, but this seems like a simple foolproof way.
You can find more information about how to code for this in an example on their website:
Good luck! 34 steps??? Do you at least have different views in a Kanban board for the different stages of the workflow?
You need a condition that can look at the date of the last transition and block the next one until the time has passed.
There isn't one of these in Jira and I've not seen one in any plugins, so you need to have a look through the marketplace for one in case I've missed it, but probably write your own. As usual, I'd recommend a look at the script runner plugin to make it easy to write your own.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs