I setup an automation in our service management project with the intention of automatically routing tickets to a separate project. Since users copied on the emails are added to the ticket as a requested participant automatically this seems like a logical approach.
Trigger: When: Issue Updated
Condition: Request participants contains any of
Action: Create a new ticket in the different project
And: Link issue to most recently created issue.
I used the Issue updated trigger because it's my understanding that Jira creating the ticket then adding the requested participants from the email are two separate actions. When testing the process the only feedback the audit log send is no action was performed because the ticket did not meet the conditions even though the tickets are successfully being created with the correct request participants in the service management project.
Hi @Matt Fishel
You are on the right path! The only thing that got away from your attention (although you have spotted the audit log) is that Request participant field is empty upon issue creation! ;)
You have to re-fetch the data after the creation and then place your condition etc. That will work! Let me know of the progress!
Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...
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