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; } } }

Copying fields to new issue that gets linked to existing issue

Benjamin Beach_hjz8ri

Hello, I am trying to write a rule in Automation for Jira Cloud so that when I create a new issue B and link it to an existing issue A from the create screen, the rule will copy some field from the existing issue A to the new issue B.

I have tried all sorts of variations of the rule using the Issue Linked trigger and the linked issues branch rule, and the rules say they executed successfully, but nothing gets copied to the new issue B.

From examining the audit log, I know that the Destination issue is B and the Source issue is A. In the "Copy from" action there is not an option for copy from "Source Issue". I tried "Current Issue" and that does not work.

Has anyone done something like this successfully? Thanks in advance!

Ben

Accepted answers

All comments

Mykenna Cepek

The technique I illustrated recently to answer this other question...

https://community.atlassian.com/t5/Automation-questions/Adding-watcher-to-subtasks/qaq-p/1939011

...might work in your case also.

Benjamin Beach_hjz8ri

Thanks for your reply, but this does not help me. I am not creating subtasks or any issues in the rule. My trigger is when the issue is linked, and I'm trying to copy fields from the linked issue to the issue I just linked to it.

Stefan Salzl

Hi @Benjamin Beach ,

Destination / Source depends on the linking goes inward or outward from the issue you are creating:

means:
if you create task B with link "causes Task A" --> Task A is the destination/Task B the source

if you create task B with (inward) link "is caused by Task A" --> Task A is the source/Task B the destination.

In order to provide a fitting solution it would be good to know the exact requirements (is there a specific link you want to match/catch?)

Best
Stefan

Benjamin Beach_hjz8ri

Hello Stefan,

Thanks for your reply. I was originally using the "relates to" link, but the inward and outward links are the same. So I was just testing without specifying a particular link type, and got the same results. But the copy function only lets you choose from "Current issue, Trigger issue, Parent issue, Epic issue, or Destination issue" Which would you use for source issue?

I appreciate your help!

Ben

Stefan Salzl

Hi @Benjamin Beach ,

one more question from my side:

should this rule be limited to the the case where link is set during creation of a new issue or should this always be triggered when linking is set (also in already existing issues) ?

This might be an important requirement to choose the right trigger of the rule.

Best
Stefan

Benjamin Beach_hjz8ri

Hello Stefan,

I would like for it to trigger in either case - when linking an issue during creation or adding a link to an existing issue. In both cases, I am looking to have fields copied from the issue I am linking to.

Thanks so much!

Ben

Welcome!

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

Quick Links

Find more posts tagged with

issue-link

automation