Forums

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

Automated Update of the ticket status by changing a linked issue from another project

katharina.stech
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 16, 2024

Hello all,

the issue is as followed:
We have 2 different boards in two different projects and with different status. Only the status in Progress and Done are named the same.

We would like to create a ticket in Board a in project a and create a child issue to board b in project b.
When the status of ticket in board b changes to in Progress or to done the parent ticket in board a should also be updated (the status).

Is there any possibility to solve this issue with an automation?
Both boards are project-managed boards

Greetings

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 16, 2024

Hi @katharina.stech -- Welcome to the Atlassian Community!

Yes, that is possible.

To confirm, are both projects Company-managed or Team-managed projects?  You may find this information by viewing the complete list of projects.

For a rule to view and update issues in multiple projects, the rule needs to be global or multiple-project in scope.  Your Jira Site Admin will need to configure a rule with those scopes.

 

The rule could then be triggered on Issue Transitioned, check the projects with conditions (so the updates happen in the direction you want: transition child issue in Project B --> results in update of the parent issue in Project A.

If both project types are Company-managed, the status values are shared even when the workflows are different, leading to a simple rule.  If one (or both) of the projects are Team-managed, the status values are distinct for each project, requiring the status id values to be used rather than the status names.

 

Kind regards,
Bill

Suggest an answer

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

Atlassian Community Events