How do I stop cloned stories from populating the active sprint?

Kenneth Huie February 4, 2022

In preparation for the next sprint I want to clone some stories that are in the active sprint. But when I select to CLONE a story in the active sprint (aka Sprint Backlog) the new cloned story is added to the active sprint and there is no choice in the matter. Which makes little sense to me given that will automatically cause a scope change. Instead Jira should provide the option to add to active sprint backlog or place the item in the backlog below. 

 

The steps I take are:

  1. open the existing task (the one in the Sprit Backlog) that I want to clone, and then type (.) to open the Actions window.
  2. I then choose Clone & select to include the sprint value and sub-tasks
  3. The story is then cloned and added to the active Sprint Backlog. 

1 answer

0 votes
Florian PEREZ
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 5, 2022

Hey, 

 

This seems absolutly normal. By cloning this ticket you get all the fields too, including the sprint field ( even if this is not shown on target project ).  

Sprint are global, you can use whatever issue from whatever project you want as it is build on the sprint field value.  

If you want to kick out the issue from the sprint you need to empty the sprint field on the cloned issue (warning:  it will change the scope of the sprint if it's live). This way you should not see the issue in the sprint. 

Remember that cloned issue gets all fields from the original issue even when not shown on target project !  

 

Hope this help ! 

Joseph Colletti
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 10, 2023

I agree with this issue.  Sometimes I want to copy an issue from the active Sprint into the backlog and just change a couple things.  I end up having to create a new story and copying and pasting each field.  Because if I clone it changes the scope of the current Sprint and messes with all the numbers.  When you choose Clone, it should default to the backlog and let the user put it wherever they want.

Like s.hennessy likes this
Florian PEREZ
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 13, 2023

You may want to try a clone by transition or by automation / script. 

you’ll need to mimic the clone action of Jira and clone your action this way instead. 

this is not perfect but this may be the best way to clone the issue without the sprint field ! 

Suggest an answer

Log in or Sign up to answer