Reopen: set recent sprint as default
Our developement only works on the aktiv sprint.
If a solution doesn´t fix well, the testers reopening the ticket sometimes forget to put it in the aktiv sprint again.
How can I set the "activ sprint" as default for reopening a ticket?
Or setting the field "sprint" as necessary to save the change?
You can easily set the Sprint field as required to transition a ticket back to the Open status. You can also automatically clear out the Sprint field on that transition to force the ticket back into your backlog.
Caveat: to set up validators, you must be a jira-admin or site-admin. To set up automation rules, you need to be a project admin.
If you want to make the field required, you just need to add a validator to the transition.
If you'd prefer to just clear the Sprint value and force the issue into your backlog, you can use the built-in automation that was recently added to Jira. Go to Project Settings -> Automation, and add a rule that looks like this (I wasn't in a project that had an Open status; you would set the trigger to When Issue Transitioned to Open).
I nearly missed this question as it is linked to Atlassian Cloud Migrations - you may like to retag this with the Jira Software and the hosting version that you use.
Whilst I can understand that when an issue is tested it can fail but I am wondering if this exposes that your team is not sharing a "Definition of Done" that includes the completion of testing.
I wonder if it would be better in your situation for the testing team to clone the ticket and report the failure as a new requirement to be fixed?
Alternatively you can look at the workflow options that are available to the user when an issue is in your "done" status and adjust these so that they do one of the following
1. require the user to either update the sprint field
2. set the sprint to the current sprint on transition
3. clear the sprint field so the item would then go in to your backlog.
To make some of these you may need to use one of the scripting plugins to automate that change.
I can see challenges with each of these approaches under different circumstances and so I would suggest you look (as a team) at how you wish to work.
Hope this provides you with pointers to how to approach your issue. I am sure others will also contribute other approaches and it is important to realise that the approach that works for your whole team will be the best one.
Happy Migrations Month ! If you haven’t heard, this January we’re hosting exclusive events, giving away cloudies, and sharing helpful resources as part of our #CountdownToCloud celebration. H...
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