Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-92335

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

XMLWordPrintable

    • 6
    • 13

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

      -

              Unassigned Unassigned
              mgocevska Maja (Inactive)
              Votes:
              238 Vote for this issue
              Watchers:
              97 Start watching this issue

                Created:
                Updated: