Our Jira tickets follow a Workflow from Open, In Progress etc ultimately through to Closed, however we have a conflict between the needs of the Dev team vs the needs of the Test team in that the Test team really need the tickets to stay in an un-closed state until they have signed them off in the System Test environment, which might be at a later point in time from when the tickets are being developed in the Sprints. As such we have an additional step prior to Closed called "Awaiting Acceptance". However, for the Dev team, this means that the tickets remain in an un-closed state and therefore show up in the Sprints until they have been signed off by the Test Team. This means that every time a Sprint is closed, all of these tickets get moved to the new Sprint as they are still effectively Open.
We can filter the list to only show Open, but it's quite messy, by the end of a 3 or 4 sprint cycle when we're ready to actually release that code there could be potentially hundreds of tickets in the last sprint.
What we tried was to create a separate Sprint (not started) called "Awaiting Signoff/Release" which we can move tickets to so that they don't clutter up the active Sprints.
What I'd like to do is creation an automation on Sprint Closure to automatically move all tickets that are in the "Awaiting Acceptance" stage (as they are effectively Dev complete) to the "Awaiting Signoff/Release" sprint, rather than just rolling them forward in to the new sprint. Any tickets at any stages before that (i.e. Open, In Progress etc) would just roll in to the next sprint.
I tried adding an automation rule and got as far as an "Edit issue" action to set the Sprint, but I don't appear to be able to set a specific Sprint in there (by name) - it only has options to select the active, or next sprint? I'm also not sure how to apply the rule to only apply to the tickets in the specific state.
Any advice? Or suggestions for a better approach.
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
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