Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Updating a ticket based on linked issue's status

Hello JIRA community, 


I am trying to figure out how to solve for a particular use case and am wondering if anyone else has ran into a similar problem. For context, we have two projects used for:


1. Feature requests

2. Development work


The idea is that we will get users submitting requests to project 1 and when we approve the request, it will create a ticket in project 2 and link it to the ticket in project 1. What we'd like to be able to do is either update the status of the ticket in project 1 (ticket A) when the linked ticket (ticket B) is transitioned to the workflow.

I know we can update a custom field as a post function for project 2 transitions but there are cases where a ticket in project 2 may have linked issues unrelated to project 1 and it seems like this might cause problems.


Does anyone have any suggestions for how to handle this? 

4 answers

1 accepted

1 vote
Answer accepted

I'm coming across the same need for almost the same scenario. So I gave the automation rules a crack and, yes. It does appear to be possible. 

Here's my code



It's worth noting that in order to make this work, the rule's scope must be set to All Projects. (in other words, global) This means you also need to be a Jira Administrator in order to make such a rule. 

This works for me, because I'm not trying to kick off any further workflow progression in the source project. Instead, I'm relying on the notifications of the source issue's Assignee and Watchers to acknowledge the generic comment and perform any needed investigation. Doing it this way is a lot more flexible to work across any issue type or custom workflows. 

Hope that helps

Does anyone have an example of how you could do this with automation? I don't see anything in there that easily accomplishes this. I think the difficulty comes when I want to ensure that the linked issue only updates the status in Project 1 not any linked issue.

The automation rules allow you to create this easily. You can do it at project or instance level

I´d suggest Automation.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events