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

automation - prevent automation rules create a issue if already created one similar Edited

i want to create a issue in a specific project (AYISA) when a specific user ("PEPE") add a comment on any project. This is a global rules and trigger with "add comment".
I want to have a clone of the original issue commented, not interest in the comment itself.
The problems is when user add another comment in the same issue, automation rules create a new ticket. That is what i call "duplicate issue" and i dont want this new ticket.
In other word, if a particular issue trigger automation rules (means clone was created in AYISA), do not trigger that rules for that issue anymore.
It is possible?
thanks in advance

 

Selection_999(1124).png

2 answers

I think something like when automation rules is triggered for first time (means specific user add a comment) in the clone issue add a custom field populated with the {{issue.key}}. If triggered again from the same ticket, compare that field with the source issue.key and if the same don't create new issue, do nothing.

IMPORTANT: I cant touch source issue. (cant add a label or something)

1 vote

Hi Federico,

So I reckon the best way to solve this, is by linking the two issues and then adding a 'Related issues condition' to your rule to check if a linked issue already exists.

So a rule like this would work:

  • Trigger: Issue commented
  • JQL condition (like you have today)
  • Related issues condition that checks *no* linked issues exists (could also use JQL here)
  • Clone the issue to AYISA
  • Link the most recently created issue to the trigger issue

 

Hope that helps!

Cheers,
Andreas

Suggest an answer

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

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

131 views 9 10
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