I know JIRA has a concept of "dependencies" between issues. We have some users who would like to automate the opening of issues based on these dependencies.
For example, let's say you have 100 issues in your JIRA project. All issues would start in a (custom) 'Wait' or 'Not Ready' state.
After the first 10 issues are complete (marked 'Resolved' or 'Closed'), the next 10 issues would flip from some sort of (custom) 'Wait' state to a 'Ready' state. After these 10 are complete, another group would flip to a 'Ready' state.
I understand this would probably involve some sort of custom issue states, but is there anything that allows for automating the changing of JIRA issue 'Status' fields as I am describing? We are currently using an older version of JIRA (5.2.5) but are in the process of upgrading if that matters at all.
I don't know of any native way of doing this. One way to do it is to create a postfunction on your transition to Closed or Resolved that fires a script. That script would count the number of closed issues matching your criteria and change the status of issues matching another set of criteria.
To achieve this, you will need the custom status you were talking about and a plug-in like Script Runner (https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner) would be helpful.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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