Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Transition an issue where linked issue has different workflow and status

Rich Candido April 2, 2025

On a JIRA project, I have an automation rule for when an issue is transitioned, the linked JSM project should change status when the status is updated to on the JIRA project.

However, the 2 have different workflows and status values, so "copy from trigger issue " doesn't work for any status that isn't the same on both projects.

Is there any way to "translate" between the two for the various status values within the rule? If the JIRA project status transition is to value "DEVELOPMENT", can the rule update the status on the JSM project to "IN PROGRESS"?

 

4 answers

1 accepted

1 vote
Answer accepted
John Funk
Community Champion
April 2, 2025

Hi Rich - Welcome to the Atlassian Community!

You don't have to use the "copy from trigger issue" just use the actual status you want to transition it to in the JSM project. 

If you are looking for some type of "translation" between them, then just add a series of  conditions where  the Status is Development then you have an action to Transition to In Progress, if Status is In Review then Awaiting Approval or whatever those look like. 

Also, it is ALWAYS helpful if you post screenshots of the rule when looking for assistance. 

 

Rich Candido April 2, 2025

Thanks John - sorry, I'm new here: Here's the rule:

Rule.png

 

If I understand you correctly, I should choose the JSM status in the displayed drop down instead of using "Copy from trigger issue" but the JSM status values aren't listed there - I assume since I'm on the JIRA project where the rule is. 

How do I denote the JSM status in this component?

John Funk
Community Champion
April 2, 2025

You need to edit the Rule Details to add the JSM project (multi-project).

Rich Candido April 2, 2025

Ahh - this needs to be a global rule and not on the project, correct?

Like John Funk likes this
John Funk
Community Champion
April 2, 2025

Not necessarily global, but yes, more than just a single project, correct. 

Rich Candido April 2, 2025

OK - tried that and it didn't do anything, but did not produce an error. I put multiple conditions under the same branch first:
Rule1.png

Then tried putting the "status is one of" checks at the component level with a branch for each conversion. 

Rule2.png

They both say "No Action performed" in the audit log. I'm sure I'm doing something wrong - hopefully it's something obvious?

Rule3.png

 

Rich Candido April 2, 2025

OK - never mind - I figured it out - I was missing the correct "Link Type" for the linked issue.

Like John Funk likes this
Rich Candido April 2, 2025

@John Funk 

I'm still not sure if the correct way is to have all of the conditions on one branch or separate the branches?

 

Can you let me know the preferred method please?

John Funk
Community Champion
April 2, 2025

Sorry, it needs to be an IF/ELSE set of conditions. Because if it doesn't meet the first condition in your second rule it just stops there. But the second one is the way to go just use he IF/ELSE for each one then move your branch under the appropriate IF. 

Rich Candido April 2, 2025

OK - thanks for your help.

Like John Funk likes this
0 votes
oscarhakinn1 April 2, 2025

But the second one is the way to go just use he IF/ELSE for each one then move your branch under the appropriate IF. 

0 votes
oscarhakinn1 April 2, 2025

more than just a single project

0 votes
oscarhakinn1 April 2, 2025

hello

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events