Issues transitioning a linked issue to a new status via automation in Next Gen

[David Washburn]

I have two next gen projects (let's say A and B) with identical workflows. I have created an automation that:

• Checks to see if an issue in project A has been transitioned
• Branches and targets the linked issue in project B
• Attempts to transition the issue in project B to a matching status

The issue is the automation cannot find the status even though both statuses have the same name, since Next Gen has different status ID's for each, I assume. Is there a way to do this so both tickets stay in sync?

Note in this screenshot I have it set to copy from trigger rule but I have also attempted to manually select Work in Progress from the list of available statuses and it still does not work.

[Hana Kučerová]

Hi @David Washburn ,

I don't think this is possible - your assumptions are correct - the projects don't share the configuration, ids, they are completely separated. It makes sense to me to share the workflow - then one automation rule will be enough to keep issues' status synchronized. Is it possible for your to change from next-gen to classic?

[David Washburn]

Hey @Hana Kučerová  the strange thing is I can get it to work with done and some other default statuses. It seems like this would be a major flaw if cloud automation doesn't support transitioning tickets with other workflows.

Otherwise isn't that what Jira's pushing for? The ability to automate actions in one place and transition linked tickets in another?