Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to automate transitioning all issues in a specific status when a specific issue is closed?

Michel January 30, 2023

I want all issues in the status "Business Test" in a specific release to go to the status "Ready To Release" when the issue with the issue type "Release Notes" inside the release (always only one per sprint) is closed.

Mainly I don't know how to be sure that only the issues in the same release version of the Release Notes issue will change the status.

I didn't manage to make it work, so any help I appreciate a lot.

Thank you in advance.

1 answer

1 accepted

1 vote
Answer accepted
Mark Segall
Community Champion
January 30, 2023

Hi @Michel 

I want all issues in the status "Business Test" in a specific release to go to the status "Ready To Release" when the issue with the issue type "Release Notes" inside the release (always only one per sprint) is closed.

This bolded section has me a bit confused.  Can you please clarify your definition of "Release"?  Are you referring to issues tagged with a specific fixVersion or are you referring to issues in the same sprint?  Having alignment on this will help me provide the right response.

Michel January 30, 2023

Hi @Mark Segall!

Yes, I changed the words in my question but I forgot this one.

Actually, I wanted to say only release (fixVersion) and not sprint.

So, every fixVersion has only one issue with the issueType "Release Notes", and when this issue is closed I want that all issues for this issue's fixVersion change the status to "Ready To Release".

I didn't find a way to do this and change the status only for the issues in the same release, I am afraid to make the automation and change the status for all issues in my Jira.

Thanks in advance Mark!

Mark Segall
Community Champion
January 31, 2023

Perfect... Thanks for the clarification.  You could go about it like this with automation:

  • TRIGGER: Issue Transitioned (to Closed)
  • CONDITION: Issue Type = Release Notes
  • BRANCH (JQL)
    • fixVersion IN ({{issue.fixVersions}})
    • ACTION: Transition Issue (Ready To Release)
Like Michel likes this
Michel January 31, 2023

Hi Mark!

Thank you a lot!

Only one question, would this "Branch rule / related issues" below work as well?

automation.PNG

 

Best regards.

Michel January 31, 2023

An alternative would be when we release a version in Jira, but I don't know how that "Fix Issues fixed in version" works. What do you think about this option below? Or should I use also that JQL you sent?

 

automation.PNG

Mark Segall
Community Champion
February 1, 2023

To be honest, I haven't tried that branch with an issue transitioned trigger.  Do you have a test environment where you can prove it out?

Like Michel likes this
Michel February 1, 2023

I created a test project to test, but it didn't work and I don't know why.

The error in the log says this:

Branch rule / related issues
Can't branch rule as it requires a version in the context for this option. More than likely you have a trigger that isn't version related. Creating a version does not put it into the context, you have to branch on it directly.
But your solution is working and it is enough for me, thank you Mark!
Best regards.
Like Mark Segall likes this
Mark Segall
Community Champion
February 1, 2023

I had a feeling there was some reason why that branch wouldn't work.  Thanks for verifying and happy my proposed solution worked for you.

Like Michel likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events