Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create one JIRA ticket for multiple JIRA automation rule invocations

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.

2 answers

1 accepted

0 votes
Answer accepted
wwalser Atlassian Team Aug 20, 2020

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:

  • The concurrency originates outside of Jira, at the octopus deploy.
  • All deploy jobs may not be finished when the initial automation kicks off.
  • At the automation level, multiple automations can be running at the same time.
  • Jira can be async + concurrent itself.

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?

0 votes
John Funk Community Leader Aug 18, 2020

Hi @amoiz  - Welcome to the Atlassian Community!

Can you share some more details as to what you have already? Maybe some screenshots?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

335 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you