While our company releases regularly, there are some ad hoc releases at times and also associating resolved issues with a new release manually one-by-one is cumbersome and also easy to miss/forget. That is the pain point at hand with this question.
Our current process with regards to releases is to first, manually create a set of future releases (which need to be continually created, a manual process that can be messed up). We release on Tuesdays, so this means that there is a future set of releases for Tuesday of every week going forward. We then associate issues with the next scheduled release when we resolve resolve the issue, so an issue resolved on Wednesday would be associated with the following Tuesday's release. However an ad hoc release could come sooner, for example on Thursday, and then the issue is incorrectly associated with the scheduled release (next Tuesday), rather than the ad hoc release (on Thursday).
My imagined workflow is that when an engineer resolves an issue, it is not associated with a release yet. Then, when the company is going to do a release, scheduled or ad hoc, they could create a new release and automatically, all resolved issues that aren't already associated with a past release would be associated with the new one. Possibly it could be limited to issues marked as resolved since the last release, but I'm less certain of that.
Is there a tool/process/feature to accomplish this desired workflow?
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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