-
Suggestion
-
Resolution: Duplicate
-
None
-
None
If you clone, the cloned tickets goes next the the position of the basic ticket.
Users want to select, where the new (cloned) ticket should be placed (in a current sprint or in the backlog).
Main Problem: If you clone a ticket in a running sprint, the reporting (Burn-Down) is completely destroyed. First effort is added and then reduced immediately, if you remove the cloned ticket (just in the same minute it is counted)
- duplicates
-
JSWCLOUD-6541 Ability to clone an issue without cloning Agile sprint information
- Closed