-
Suggestion
-
Resolution: Fixed
-
None
-
EACJ
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
Original summary Cloning an issue also clones Agile sprint information
- causes
-
JSWCLOUD-10548 Cloned issues inherit the Completed Sprint value and can't be removed
- Closed
-
JSWCLOUD-10694 Allow issue to be removed from completed sprint
- Closed
- is duplicated by
-
JSWCLOUD-7307 Cloned Stories retain values of Sprint field from parent issue
- Closed
-
JSWCLOUD-9835 Cloned Issue is appearing in the Active Sprint
- Closed
-
JSWCLOUD-10682 Do not include completed sprints when cloning issues
- Closed
-
JSWCLOUD-7707 As a user I want to be able to clone a ticket already assigned to an active sprint but given the option not to include it in that sprint or instead place in top of backlog
- Closed
-
JSWCLOUD-9556 Clone a ticket should ask where to place new (cloned) ticket.
- Closed
- is related to
-
JSWCLOUD-10935 Ability to move an issue without copying Agile sprint information
- Closed
-
JSWCLOUD-12196 Split an issue and its story points into parts whilst maintaining state
- Closed
-
JSWCLOUD-13625 Add "Create Linked Issue" option to Software Projects
- Closed
-
JSWSERVER-6541 Ability to clone an issue without cloning Agile sprint information
- Closed
-
JSWSERVER-19903 Ability to clone an issue without cloning Agile sprint information
- Closed
- relates to
-
JRACLOUD-41150 Update Clone Issue Docs to include or link to JIRA Agile caveats
- Closed
-
JRACLOUD-43019 Option to purge the sprint field while cloning issues
- Closed
-
JSWCLOUD-11770 When cloning issues, clone the position in the backlog
- Closed