Darshan Hiranandani : Automate Copying a Field Value Between Projects on Issue Transition in Jira

Question

Hello everyone,

I have two projects in Jira: Project A and Project B. I want to set up an automation rule where, when a story in Project A transitions to the status "Committed", it should look up a linked "Initiative" in Project B. Once it finds the linked Initiative, the automation should retrieve a value from one of its custom fields and copy that value back into a specific field in the story in Project A.

I’ve started working on an automation rule, but I’m having trouble completing the setup. Specifically, I'm not sure how to properly reference the custom field value in the linked issue from Project B and copy it back to the story in Project A.

Does anyone have experience with this type of automation or can offer pointers on how to achieve this?

I’d really appreciate any help or suggestions!

Thanks in advance!

Regards

Darshan Hiranandani

Trudy Claspill · Answer

Hello @Darshan Hiranandani

When asking for help with changing an automation rule, we need you to provide specific information to enable us to provide that help. Please provide he following:

1. A screen image that shows your entire Automation rule.

2. Screen images that show the details of each step of the rule.

3. Information about the project(s) referenced in the rule. What is the Type of each project referenced?

4. Screen images showing the details from the Audit Log for the rule execution, if you are executing it and not getting the results you expect.

5. Tell us about your environment. Are you using Jira Data Center or Jira Cloud?

6. Tell us about your level of access. Are you a project administrator or a Jira administrator?

In this case you have said that the trigger issue is in one project and the linked issue is in another. You will need to set the rule up as a multiple-project scoped rule. Those can be created only by Jira Administrators from the Global Automation page. Are you a Jira Administrator?

How are the issues linked together? Are you using generic issue linking, or have you created an issue type hierarchy that allows the issues to have a parent/child relationship?