Save the custom field details when using Split issue feature in Backlog

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: None
    • 10
    • 24

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

      -

              Assignee:
              Unassigned
              Reporter:
              Maja (Inactive)
              Votes:
              255 Vote for this issue
              Watchers:
              131 Start watching this issue

                Created:
                Updated: