Sending Different Release Notes with Different Tickets for a Fix Version to Different Groups

Maria RoseGrows
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 26, 2024

Hi all, hopefully I can explain this well!

We send out release notes to different groups in our org (Claims, Operations, Sales) Some tickets in the Fix Version should go out to one or more of these groups but we don't want to send release notes to those who don't need to see them (Eg. Claims doesn't need to see Operations notes unless they're both in the "Release Communication Planning" field. We create a "Pre-Release Communication" ticket where we then run the automation. The problem is we have to go into this automation every time and edit the "fixVersion in" Here's an example of our current logic...

Screenshot 2024-04-19 at 3.41.58 PM.png

Is there a better way to do this that we don't have to keep going in and editing the fixVersion in the automation in order to send these notes out? 

1 answer

1 vote
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 27, 2024

Hi @Maria RoseGrows and welcome to the Community!

If your trigger issue has a reference to the version you are releasing, you may indeed be able to refer to that version using a smart value in your lookup issues action.

You could consider changing the JQL filter to:

... and fixVersion in ("{{}}")

I am making the assumption that you would also use the fix version field to refer to the release and that your communication issue would only apply to 1 version. If these conditions are met, I would expect this to work.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events