Remove Complete Sprint

Jose M.
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.
September 28, 2014

The following problem:

One issue in one Agile Board.
Cloned and moved to another project and Board.
It still includes the information from both Sprints.


How can I remove the obsolete information from former Sprint, before the issue was cloned?
Note: The former Sprint in the other project is already completed, so not editable in the issue edit Screen.

Is this the current behaviour in JIRA and Agile to clone the Sprint information also?

Thanks for any help!

 

3 answers

1 accepted

0 votes
Answer accepted
Jose M.
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.
September 28, 2014

There is a workaround described. Obviously even Atlassian does recommend to use it in the meantime:  Clone issues inherit Completed Sprint value and can't be removed (GHS-10548). I succeed to remove the completed Sprint from the Sprint Field.

1 vote
Luther Hargrove
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.
September 28, 2014

The sprint field is definitely going to be cloned if you clone an issue.  It's just a value in the issue that can be set.  If the sprint field is on the edit screen, you can edit the issue and remove the value from that field.

Jose M.
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.
September 29, 2014

Thanks for confirming the behaviour of Jira, nevertheless it is a problem, if you can't remove that termporary information. We are glad there is at least a workaround to remove competed sprints.

0 votes
Jose M.
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.
September 28, 2014

This problem was already reported to Atlassian, almost 2 years ago: Cloning an issue also clones the GreenHopper sprint information (GHS-6541)

 

Suggest an answer

Log in or Sign up to answer