Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

what is the difference between a clone and a duplicate?

When linking two issues on JIRA, what is the difference between one issue "cloning" another, and an issue "duplicating" another?

2 answers

1 accepted

12 votes
Answer accepted

A clone is derived from the clone issue operation. A duplicate is an independently entered issue which has the same content (same problem).

How do you clone an issue, and why would you do that?

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)

Like # people like this

Hello,  I see, that's it's been some time, but still.

@Nic Brough _Adaptavist_

"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)?

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.

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? 

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.

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?

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.

Could you kindly elaborate on this explanation

I didn't understand which field you are pointing at. If you could just explain that in your answer

I can't.  The explanation is answering a question about field data during a move, not for a specific field, but for any field you might have on an issue.

Hi there, can you tell me how we can get the comments to move as well when we clone?

My example is, i've got testing cards that have bugs, I want to clone the testing card to turn it into a bug card but all the testing failures in the comments do not copy over?

Or am i better to create a task from the testing card? Thanks.

The comments do not get copied during "clone" because they are a converstation about the original issue, not a conversation about the new cloned one.

Cloning issues is for an edge-case where you need a copy, it's not for duplicating existing work.  Cloning to turn test cards into bug cards is a broken process - you should be fixing the broken tests, not copying them.

Thanks Nic.  I've read suggestions to create a sub task called Sprint Bugs.  Will do this and add them to the testing card as the testing card is pretty broad.  Any other best practise suggestions are welcome.

8 votes

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)

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you