Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Reopen: how to set recent sprint as default?

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?

2 answers

1 accepted

0 votes
Answer accepted

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.

2020-07-10 12_07_47-Add Validator To Transition - Jira Staging - Vivaldi.png2020-07-10 12_08_31-Add Workflow Transition Validator - Jira Staging - Vivaldi.pngIf 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).

2020-07-10 12_11_42-Project automation - Jira Staging - Vivaldi.png2020-07-10 12_11_25-Project automation - Jira Staging - Vivaldi.png

2 votes
Phill Fox Community Leader Jul 10, 2020

Hi @Christian Messer 

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. 



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events