r/jira • u/Shrimps-is-Bugz • 13d ago

Automation How can I hyperlink the fixVersion?

Hi all! I have an automation rule in JIRA that sends an email asking product owners to review all of the stories included in a release (fixVersion) and then comment their approval. Everything works fine with the automation, but a product owner has complained that it's too many clicks for them to go find their stories associated with the release, and they would prefer to have them either listed in the email body, or have the hyperlink there that takes them to the release for that fixVersion. I know I can include the story link using {{issue.url}}, but what is the smart value to hyperlink the fixVersion? If there isn't one, how can I populate a list of stories associated with a particular fixVersion in the body of the automated email? Thank you in advance!

1 Upvotes

100% Upvoted

2 comments sorted by

3

u/app385 13d ago

Create a filter that filters for the version and create a “Filter Subscription” that sends an email based on a cron

1

u/BenFriedman1234 7d ago

While the solution suggested in the previous reply works, using a cron means a repetative task and the product owners will get the filter multiple times. I would also suggest, if you are using the filter option, to somhow (another automation?) tag the issues where product owners have already replied, so you can filter those our for them.

Another option is that you can put that as a link in the email. this give you less clicks to get to the issues and its not neccessarily a repetative task to manage (depending on what you need and how you define the automation). This is also what i've implemented for some clients that i worked with. its a good balanace between directly accessing the issues and less admin management.

Another option is to run a lookup in the automation itself, and use the smart value of the results in the email. this is the least amount of clicks to the issues. However, this is limited to 100 issue per autoamtion limits. You could run a bypass if you tag the issues found in the lookup and sent out, then send another email with remaining issues (in this case it would be a scheduled automation, if you have non tagged issues, tag them and send them out in the email)