You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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
Hi All, We’ve heard you when you said that it takes too long to make changes to multiple issues - given that you’ll have to open them one by one to make changes. With this release, we are addressin...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.