[JIRA Automation] Update field in Project A and autotransfer info to field in Project B

[JD]

Hi!

I have custom fields in Project A, e.g.:

• Release Date (date picker field)
• Product Owner (drop-down/search directory field)
• Product Marketing Manager (drop-down/search directory field)

And I want to port them to the 'Description' field (paragraph field) in Project B.

I worked on the automation to port the Release Date, Product Owner, and Product Marketing Manager fields of Project A into the 'Description' field Project B but wanted to know if I can set up automation to auto-update the 'Description' field in Project B with the refreshed information if Release Date, Product Owner, or Product Marketing Manager update in Project A. The ticket from Project A and B also need to continue to be linked.

Thanks in advance! 

[Bill Sheboy]

Hi @JD 

That may be possible when:

• your rule has at least multiple-project scope in order to access issues in both projects
• the Description field has a format / structure which allows parsing to find and update the information from the other issue

The rule would be triggered on a change to your field(s), test if the project is the "source" one, and then find / replace the value in the Description.

Kind regards,
Bill

[JD]

Thanks Bill! The first is trie where the rule has multiple-project scope. Which option/path would I be able to use to trigger this automation? I did not see a 'If x field changes in Project A,' then update 'Description' field in Project B. Appreciate your help.

[Bill Sheboy]

There is no such action to do exactly your scenario.  The key is identifying the "target" issue in "Project B" to update.

Instead it could be something like this:

• trigger: issue field changes for Release Date
• condition: project is your "Project A"
• branch: somehow branch to the issue in "Project B" (e.g., with links, JQL, etc.)
  • action: edit issue, parsing the Description field with text functions to replace the value of the Release Date.  This might require multiple steps and will certainly require the use of text functions.

Here I am assuming you are trying to update a specific issue in Project B which is somehow connected / linked to the issue in Project A.  Is that what you wanted to accomplish?

[JD]

Yes - thank you Bill! I will test this out.