nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Replicate custom field value in linked issues

Leonardo Zevallos Guzman

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?

Accepted answers

Ste Wright

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

All comments

Ste Wright

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

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

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

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud