Forums

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

Replicate custom field value in linked issues

Leonardo Zevallos Guzman
Contributor
November 22, 2023

Hello community, I need help with an automation:
My context is the following I have 2 projects Project A(Jira Work Management) and project b(Jira Software) . In my project A I manage the master of all the projects in the area and in project B it can be a development project What happens is the following in my project A I have tasks with names of many pending, when a pending needs to be escalated to a development of software, that task is linked to project B. I need certain custom field values ​​like the "requesting area" to be replicated from my task in project A to the user story in project B. Both projects manage the same fields.
Could someone tell me the steps to follow in the automation rules?

 

1 answer

1 accepted

0 votes
Answer accepted
Ste Wright
Community Champion
November 22, 2023

Hi @Leonardo Zevallos Guzman 

This is possible using Automation - can I confirm though, is the rule...

  • When escalated, clone the Issue from Project A to B, or...
  • When escalated, an Issue Link is added (linking two issues from A/B)
    • If yes, what is the link type and what are the inward/outward descriptions?

This information can help define how the rule should work :)

Ste

Leonardo Zevallos Guzman
Contributor
November 22, 2023

Sorry for my answer in Spanish

Hi @Ste Wright The rule would be:

.When you link task from Project A to the user story of Project B. The value of field "X" that already has a value configured in Project A is copied to Field "X" of the edition of project B.

The type of link would be clones. What do you mean by internal and external descriptions?

Ste Wright
Community Champion
November 22, 2023

Hi @Leonardo Zevallos Guzman 

The rule would look something like this in that scenario:

  • Trigger: Issue Linked
    • Link Type = Cloners
  • Action: Edit Issue
    • Field = Field Here
      • Value = COPY FROM
        • Issue to copy from = Destination Issue
        • Field to copy from = Field Here

---

A few notes on this rule:

  • The trigger Issue Linked allows for actions to be performed on either the source or destination issue. The source issue is the master in automation - this is defined as:
    • Issue A is cloned by Issue B
  • You can send data to the destination issue, using a Branch
  • The COPY FROM option in the Action can be found through the breadcrumbs (...) in line with the field name. Once set, click on the box to edit the "copy from" values

---

Let us know if this works for you!

Ste

Leonardo Zevallos Guzman
Contributor
November 22, 2023

Captura de pantalla 2023-11-22 201514.png

 

In which part do I order the Project B incident to copy the data from the Project A field. When I link From Project A to Project B. I couldn't understand what he told me

Ste Wright
Community Champion
November 22, 2023

Hi @Leonardo Zevallos Guzman 

Click on the box "Copy Source Type from Current Incident"

A pop-up will appear, and you want to choose to copy the data from the Destination Incident.

Ste

Leonardo Zevallos Guzman
Contributor
November 22, 2023

The rule causes the value to be changed in the Project A issue. The objective is to change the incidence of Project B.
Because from an incident of Project A I link to an incident of Project B.

Ste Wright
Community Champion
November 22, 2023

Hi @Leonardo Zevallos Guzman 

I'd give the opposite direction a try (destination issue), and see if that works - the rule would look like this:

  • Trigger: Issue Linked
    • Link Type = Cloners
  • Branch: Related Issues
    • Type = Destination Issue
      • Branch-Action: Edit Issue
        • Field = Field Here
          • Value = COPY FROM
            • Issue to copy from = Trigger Issue
            • Field to copy from = Field Here

Ste

Leonardo Zevallos Guzman
Contributor
November 22, 2023

The rule doesn't change anything.
I have configured it like this:
Regla.png

Ste Wright
Community Champion
November 22, 2023

Hi @Leonardo Zevallos Guzman 

In either scenario, what does the audit log state?

Ste

Leonardo Zevallos Guzman
Contributor
November 22, 2023

Hello! It's strange because before the audit came out like this and now it works correctly. In Jira does it take to update when an issue is edited?.The thing is that it already works, thank you dear @Ste Wright 
Regla actualizada.png

Ste Wright
Community Champion
November 22, 2023

Hi @Leonardo Zevallos Guzman 

Time to complete can vary (depending on how complex the rule is), but it can be often 5-10 seconds.

Great to hear it works though!

If this answer did help you resolve your query, could you accept it? :)

Ste

Leonardo Zevallos Guzman
Contributor
November 22, 2023

Of course, thanks

Like Ste Wright likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events