Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Cloning an issue creates a new issue in a "clone" of the current sprint

I've encountered this behavior several times, and I'm still struggling to understand what I'm seeing.  When I clone an issue, the clone is placed in a clone of my current sprint.  Specifics:

Cloned a bug this morning.  Our current - active - sprint is 2021.s8.  The bug we cloned was in sprint 2021.s7.  The new bug was placed in sprint 2021.s8.  When I opened my story board to see the contents of my sprint (anticipating seeing the newly cloned bug), the new bug was not there.

Having seen this behavior before, I went to the Backlog view, and now I see TWO sprints identically named 2021.s8; one sprint contains all my team's other sprint work, the other sprint contains only the newly created - cloned - bug.  So, I dragged the new bug into the active sprint of the same name, and now the bug shows in the current sprint... and under the backlog view, I no longer see two sprints of the same identical name.

What is going on??

1 answer

1 accepted

0 votes
Answer accepted

Is this for a Team Managed (next gen) or Company Managed (classic) project?

This is a classic project.

BTW, I am an admin, so I have more permissions than the average user...

Was sprint 2021.s7 closed, but the Bug issue was not completed so it went into the backlog?

Did you have the "Clone sprint value" box checked when you cloned the issue?


So far I have not been able to recreate this situation.

2021.s7 was indeed closed. Clone Sprint Value - I've tried it both checked and unchecked... and I believe (can't swear) the results were the same.  This morning, Clone Sprint Value was unchecked.  Once the clone was created, I assigned the clone to sprint 2021.s8 - which should have been our current active sprint - which turned out to be the "clone sprint".  When I discovered it was not showing up in our current active sprint of the same name, I did as described above and dragged it into our current sprint, at which time the "clone sprint" disappeared from view.

If Clone Sprint Value was indeed selected, does it make sense it would actually clone the sprint and place the cloned bug in the cloned sprint?  I thought sprint value had to be unique; we have sprints unique per project in our configuration; I would not have thought Jira would permit two identically named sprints associated to the same project.

JIRA does not prevent the creation of multiple sprints with identical names. You can  confirm that there is actually only one sprint in your JIRA instance with a given name by executing an Advanced Search with JQL. When you specify Sprint as the criteria and start to type in the name of the sprint, you will be shown potential matching values. If there is more than one sprint with that name, that will show in the list of matching values.

The disappearance of the "cloned" sprint from your board after you removed the issue suggest that a second sprint with the same name (2021.s8) was actually created in a different Scrum board. A sprint will show up in a scrum board if either of these conditions is met:

1. The sprint was created in that scrum board

2. The sprint contains an issue that is within the filter/scope of the scrum board, even if the sprint was created in another board.

JIRA does not prevent the addition of issues to sprints that are not part of the same board.


Doing a bit a research I found that the "Clone sprint value" checkbox is not actually creating a new sprint by that name. It applies when you are cloning an issue that is in an active sprint, and the result is that the newly created clone issue is added to the same sprint rather than being put in the backlog.

Like Bill Sheboy likes this

Well, JQL clearly shows I have a duplicately named sprint, which contains no issues.  How do I safely remove/close/delete that sprint without inadvertently causing issues with my current/active sprint?

Your notes above make sense regarding Clone Sprint Value; this was my understanding of the function of that checkbox as well... good to get confirmation - thanks.

You need to find the board where the sprint was created and delete the sprint there. I found this suggestion in a comment from @Jose Luis Casarrubias in another post:

You just need to have the sprint ID and then use rest api:/


This rest api will provide you the originBoardId of the sprint


Once you have the board ID, then you can bring up the board using the URL

https://<your JIRA URL>/secure/RapidBoard.jspa?rapidView=<board id>

NVM - I found instructions on how to do this out in the community forum... I created a bogus Bug, assigned it to the sprint, then went to the backlog, was able to see the duplicate sprint, then I deleted the duplicate sprint.  I think I'm good now.


Thanks for all your help!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

103 views 1 3
Read article

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