You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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. :)
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.
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.