Details
-
Suggestion
-
Resolution: Unresolved
-
8
-
16
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
Currently, as explained under Split Issue Backlog in Using your Scrum backlog:
The new issue will have most of the same details stored in the original issue, including priority, component, label, etc.
The issue details that won't be copied over include work log, comments, issue history, issue links, etc — though the original issue will be linked to the new issue.
Suggested Solution
The customer would like to have a copy of the custom field as well
Workaround
-
Attachments
Issue Links
- is related to
-
JRASERVER-64934 Save the custom field details when using Split issue feature in Backlog
- Gathering Interest