-
Suggestion
-
Resolution: Duplicate
-
None
-
None
I have read a bunch of other issues on improvements for cloning - however, independant of all those suggestions, the ui-flow should be such that you go to the edit issue details screen (with all of the cloned data in it) before the issue is saved...
In many cases when you are cloning, a large percentage of the issue may stay the same (hence the reason to clone) but there is usually more than just the subject that you want to edit before you save.
Currently, the only thing to do is to save - and then immediately edit - but unfortunately, the issue-creation email will have already been sent - and it wont be correct.
- duplicates
-
JRASERVER-5417 Modify System/Custom Fields when copying an issue
- Closed
- relates to
-
JRASERVER-4821 Clone issue should copy comments, due dates etc.
- Closed
-
JRASERVER-70683 Clone issue should copy comments, due dates etc.
- Gathering Interest
-
JRASERVER-5052 Allow different "Clone Issue" options
- Future Consideration