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

Update cloned issues simultaneously

Nicolas Gauvin

Hi,

I want to be able to update feilds of cloned (or linked) issues that were moved (transfered) into other projects. I have several custom feilds that will always stay the same and I'm wondering if I could set it in so when an issue is updated in 1 project, it's also updated in the other project.

In a nut shell:

A clone (or duplicate) an issue, then move it in another project (sometime when all pertinent feild were not yet all filled). This would same me a great deal of retyping concomitant information.

Accepted answers

All comments

Petter Gonçalves

Hello Nicolas,

Welcome to Atlassian Community!

I understand that you would like to update the cloned issues fields every time the source issue is upgraded. Is that correct?

Unfortunately, JIRA does not have this kind of functionality, however, there are some plugins that can help you achieve this.

My suggestion would be to use Automation for JIRA plugin and configure the following rule:

Screen Shot 2019-03-11 at 17.50.16.png

P.S: I used the Affect Version/s field as an example, put the same rule can be applied to any issue field.

Let me know if this option helps or if you have any other questions about it.

Matias Jauregui Lorda

This is exactly I needed. Thanks

Hubertus Wasmer

HI Matias,

I tried to open the link from Peter. But it is not working anymore.

could you provide me the plug in name?

best

Hubertus

andras.juhasz

Seems like there is a free plugin offered by Atlassian serving a similar purpose:

https://marketplace.atlassian.com/apps/1215460/automation-for-jira-data-center-and-server?tab=overview&hosting=datacenter

From Jira 9.0 onwards, it's an integral part of the SW, while for earlier versions it is available as a free plugin.

Emilie Corcoran

hi @Petter Gonçalves

Coming back to this comment I am unable to use the "For linked issues" piece here. I'm using "If: Linked issues present" but its not recognizing ccross-project linked issues unfortunately. Can you help?

Petter Gonçalves

Hey @Emilie Corcoran

Regarding the branch "For linked issues", you can find this by following the steps below:

Go to your automation rule > Click to edit
After adding the rule trigger, click to add a new branch > Branch rule/related issues
Select "Linked issues"

Also, to include cross-projects in your automation, you must create/edit the automation on the global administration page:

Navigate to any project > Project settings > Automation
At the top-right corner, click on global administration

Screen Shot 2022-08-18 at 1.38.22 PM.png

Under that menu, you should be able to edit the rule details and include more projects to be considered by the automation.

Let us know if you have any questions.

Sairys Bolivar

Hey @Petter Gonçalves

I did the steps you mention but I can not get the change to run, maybe my process is different, could you help me with the following case, what I need is:

The process would be to receive an incident in jira service Management, clone and move to the corresponding board, which already makes the incidents are linked, what I need is : that the cloned incident to jira software to change status, I change the status of the original incident. Is it possible?

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

jira-core