Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automatically add tickets to a Release

Assumptions: We will only have one release open at a time. 

Is it possible to automatically add jira tickets to an open release once the status of the ticket has been changed? I have a status called "Demo Ready", and once QA has moved the ticket to "Demo Ready" I would like the ticket to automatically be added to the most recent open release and add the version number to the ticket so that I don't have to go through the board to see which tickets are ready to go into the release since we do not do planned releases. 

2 answers

2 accepted

2 votes
Answer accepted

Hi @Victoria Lee 

I am assuming that you want to update the "Fix Version" for an issue which has been transitioned to the status "Demo Ready".

You can use the Jira Automation to do that.

You can use trigger as "Issue Transitioned".  Select To status as "Demo Ready" e.g.:

Screenshot 2021-04-12 at 10.52.54 PM.png


And then Select Action as "Edit Issue" and set "Fix Version" as next unreleased version. e.g:

Screenshot 2021-04-12 at 10.51.17 PM.png

1 vote
Answer accepted

Something to consider with the Automation suggested by @Deepanshu Natani is what should happen if the issue regresses. Is it possible for an issue to go backwards from Demo Ready to an earlier status, and in that case should the issue be removed from the release? If so, you would need an additional automation rule for the transition from Demo Ready to the previous status (or statuses) that would clear the FixVersion field.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

100 views 1 3
Read article

Community Events

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

Events near you