You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a JIRA automation rule associated with a octopus deploy which works perfectly fine for a lower environment when we have deployment associated with a single ticket.
Now consider octopus deployment (or a release) into QA / Staging environment which might include multiple JIRA issues. We observe that if we have 3 tickets in an octopus release the automation runs 3 times for each ticket.
My question is - Is there any smartvalue or any other way in which we can find all the jira issues associated with a deployments something like {{deployment.issuesList}}
Hey @amoiz ,
This is currently not possible to have one big trigger for multiple issues. However it is a really interesting use case. You could raise a feature request on this instance https://codebarrel.atlassian.net/jira/software/c/projects/AUT/issues
Thanks for your question
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.