nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Replicate status on cloned items in different projects

João André Amaro

Hello,

I have two different projects: project A and project B.

When an issue in project A is assigned to me, I have an automation that clones it to project B - the automation also creates a link with each other, and sets the summary and description to be the same.

Is there a way to automate the transitioning of the the issue in project B when the issue in project A is transitioned?

Example:

issue in project A moved to "IN PROGRESS" -> issue in project A should be moved to "IN PROGRESS"
issue in project A moved to "CLOSED" -> issue in project A should be moved to "DONE"

Accepted answers

Dexter de Vera

Hi @João André Amaro ,

Do this example in Jira automation:

When: Issue transition (select the status of Project A)

Branch: For: Link issue (select link issue type you use)

Then: Transition to issue (select the status of Project

All comments

Dexter de Vera

Hi @João André Amaro ,

Do this example in Jira automation:

When: Issue transition (select the status of Project A)

Branch: For: Link issue (select link issue type you use)

Then: Transition to issue (select the status of Project

Jack Brickey

Hi @João André Amaro , welcome to the Community. Yes this is certainly possible. You would need a global or multi-project rule. There are a number of posts in the Community discussing this or similar use cases. Here is one that I found as an example - When-a-cloned-issue-has-status-updated-update-status-of-original .

basically, your rule would look like this...

trigger - issue transitioned
conditions - conditions to zero in on only those issues where you want to execute the action
branch - for linked issues of type xxx
Action - transition issue , copy from trigger

one thing to note is the requirement to have a shared workflow or an 'open' workflow using "All" transition. This is so that the transition will succeed.

Dexter de Vera

make sure your automation scope is multiple project and project A, B included.

Dexter de Vera

Base on example it have different status (closed and done).

João André Amaro

It worked perfectly. Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud