I have a situation in which an octopus deployment can be associated with multiple JIRA tickets. However i don't want each JIRA automation to create a new JIRA ticket instead all these multiple parallel JIRA automation invocations should result in a single ticket.
I tried these 2 approached both failed:
a. I tried setting a flag to use it to as concurrency check
b. I also tried implementing logic by using a JQL query to check for existence of a JIRA ticket and if not create one. - In this case all the multiple invocations created a ticket
Any inputs will be greatly appreciated.
This is a tough one and I don't think we have a solid solution inside Jira / Automation. There are multiple points for currency to leak back into whatever solution you come up with:
Is there any point at which the octopus deploy collapses back to a single thing from which you could trigger the automation? Basically a way to ensure the automation is only kicked off once the whole set of jobs is truly complete?