Looking for the cleanest solution for automation

[Erin Van Note Moore]

Set Up
Creative Teams
Team 1
Team 2
Team 3

All these do creative work which is sent through a lengthy review process and can be sent back. 

Review teams
Team A
Team B
Team C
The alphabet teams can send work back to any of the creative numerical teams by sending an item to the "needs revision status, then the issue goes back to a numerical team teams status "waiting for revisions" how can I automate this for my client?

[Joseph Chung Yin]

@Erin Van Note Moore -

Based on your high-level ask, you can also just utilize Automation for Jira to create automation rule to be triggered by issue events (i.e. issue created etc) to create the process.

Here is a link on Automation for Jira - 

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

If you can provide more details on your ask, then we can assist you better.

Best, Joseph Chung Yin

[Jim Knepley - ReleaseTEAM]

Hi @Erin Van Note Moore 

I imagine you're asking because you have separate issue types for creation and review issues.

If creation and review are tracked with the same issue, then what you're asking for is done easily with an issue workflow.

If you have separate issues, it would require an extra piece of information... the review ticket would need to know the ID of the creation issue (a linked issue makes sense). Once you know that, a Jira Automation rule should be able to get that issue ID and trigger a transition on the creation ticket.