In our jira instance, our users sometimes have to clone an issue, move it to another project and then link it with the parent issue.
Now these three operations take time. I was wondering if there is a short way of achieving the same espicially since the entire process can take a lot of time if you are doing it for say 100 issues.
Thanks for mentioning the Clone-and-move plugin rambanam prasad. I had not seen that before. It looks like a good option if you need flexibility during each clone-and-move event. And it is free!
In contrast, the Create-on-transition plugin (https://marketplace.atlassian.com/plugins/org.swift.jira.cot) is a paid license, but it may also allow you to remove more of the work of cloning and moving if you frequently move clones to the same project. If you do the same kind of clone-and-move a lot, the Create-on-transition plugin is actually more convenient for the user. Once you set up a workflow transition and a postfunction for creating the new issue, it only takes one click of a workflow button for the user to clone and move the ticket. Literally one button. An added benefit is that you don't actually clone the issue. The plugin creates the new issue in the target project instead of creating it in the original project and then moving it. This avoids running up the issue key in your original project and avoids any need for tracking information to link the issue key in the original project to the issue key in the new project.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs