It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
When linking two issues on JIRA, what is the difference between one issue "cloning" another, and an issue "duplicating" another?
A clone is derived from the clone issue operation. A duplicate is an independently entered issue which has the same content (same problem).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am sorry, I do not understand the question. We've already explained that a cloned issue is a copy that might be available to customers, so I am not sure what you are asking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
May be similar to my query, for example:
I have a Test that I want to use in a different project - do I Clone it, or do I Assign it to the other project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you need to keep the original, then clone and move the clone.
If you don't want the original to stay in the source project, then move it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
When you move an issue to another project, does all the fields come over to the new project? If so, how will I see those fields, if they are not on the new project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.