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.
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.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Perfect... Thanks for the clarification. You could go about it like this with automation:
fixVersion IN ({{issue.fixVersions}})
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.