Click "clone" in the menu on the issue. It's usually done when you have a lot of information on an issue and want a copy of it. Or you want to split the work (Within the same project or to move the copy to another project). Or you have segregated data (client X needs to see the issue, but not allowed into its project, so you need a copy in a project where X can see it)
Hello, I see, that's it's been some time, but still.
"Or you have segregated data (client X needs to see the issue, but not allowed into its project, so you need a copy in a project where X can see it)"
- you mean, that the clinet X is going to see the changes I am making to a clon-issue (in a project, where can see it)?
The fields will move with the issue if the fields are valid for the new project in terms of field context. If they have no context, their content will be removed. If they do have context, the data remains on the issues, but you may still find that the project screens and/or field configuration hide them.
A clone is an issue that was created by copying another issue
A duplicate is an issue that repeats another issue (an example - it happens a lot when two clients raise the same bug - often the second/third/nth raiser doesn't know that it's already been reported)
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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