Here's the problem ...
What suggestions do you have for a configuration or automation or something (anything) that would meet all of the following requirements:
Hello @barronkid I dealt with scenarios like that in the past and you can find in the marketplace apps that can help you sync issues between two instances. That would be the pretty solution.
I recall that those weren't an option for some of our customers so in order to avoid the loops we did something like the following.
Disable the new ticket notification and create an automation that does exactly the same for all but the other Jira e-mail. That way the Jira services don't notify each other that they got the email.
I believe that we ended updating the summary as well to contain both tickets IDs so any comment would go to one or another ticket without creating a new one.
I hope I'm not forgetting any other change we did. Let me know how it goes
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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