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.
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:
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. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems like there is a free plugin offered by Atlassian serving a similar purpose:
From Jira 9.0 onwards, it's an integral part of the SW, while for earlier versions it is available as a free plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi @Petter Gonçalves
I want to replicate this automation for our Project but the "is cloned by" Linked issue Type is not available for me. How can I create or get the same?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Emilie Corcoran
Regarding the branch "For linked issues", you can find this by following the steps below:
Also, to include cross-projects in your automation, you must create/edit the automation on the global administration page:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.