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:
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 B)
make sure your automation scope is multiple project and project A, B included.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Base on example it have different status (closed and done).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.