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

Can I edit an issue in another project when a custom field changes with Automation for JIRA?

andreas Rising Star Jan 26, 2017

Is it also possible to update existing issue in other project with Automation for JIRA?

The whole rule would be if a multi-select custom field gets updated in issue in project X, then this rule would trigger and find the existing issue(s) which has the same value in field Summary in project Z and transition this project Z issue to a different status.

2 answers

1 accepted

2 votes
Answer accepted
andreas Rising Star Jan 26, 2017

Yes you can do this with Automation for JIRA.  Just make sure that you create this rule as a 'global' rule since project rules can only edit issues in their project.  To do so go to 'JIRA Administration' -> System -> Automation rules (or simply hit the '.' shortcut and type 'Automation').

Make sure the Project(s) scope is set to global.

Then you'd create a rule like this:

Automation rules - Code Barrel JIRA 2017-01-27 10-21-32.png

Here's how this works:

  • We use the 'Field value changed' trigger to monitor our 'Sample select' custom field
  • Next we have a JQL condition to ensure that we only run the rule if the field is updated in the DEMO project (my project X)
  • Then we use a 'related' issues action to find all issues in project TIB (my project Z) where the summary is the same as that select field's value 
    • For those issues we transition them to 'DONE'.


This is sooo close from fixing my issue. Can you look at my relatively similar situation.

I have a custom field 'Companies' that is brought in by a 3rd party plugin. I want to be able to update the company field when for all linked issues to the original issue created. 

In a scenario base, 
A JIRA Help Desk issue is created. 
A link is created and the attachments, description, summary and reporter are copied to a new JIRA Software Issue (separate project).
I want to be able to also copy or update or sync the original Company from the original Help Desk Issue. 

Is this possible? 

Thank you!

andreas Rising Star Sep 26, 2017

Hi Cody,

Is Company a single select field?  If so, then when you create the new issue in the software project, then you should be able to set the 'Company' field there to this smart-value (


If this doesn't work, feel free to post your current rule configuration (screenshot) to and we can take a closer look at your exact rule config.



Thank you Andreas, I'll go ahead and submit this to codebarrel support. 

Hi @andreas, thanks for this amazing solution! 

I have one more question - is it possible to affect only issues linked to the trigger issue? And can the link type/s affected be specified?



andreas Rising Star Jan 07, 2018

Hi @Alex,

Yeah so with the related issues condition, you can also specified "linked issues" as one of the options.

Or you can use JQL and use something like use the linkedIssues() function part of JQL (see )

For example: 

issue in linkedIssues({{triggerIssue.key}},"is duplicated by")


Hope that helps!




I am setting up an automation rule. 

: create an issue B from issue A by project A automation rule --> success

: edit an issue A of project A  by project B automation rule --> fail


global rule.jpg



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events