Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-64934

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

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • UIS:
      37
    • Support reference count:
      6
    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      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

      -

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mgocevska Maja (Inactive)
              Votes:
              147 Vote for this issue
              Watchers:
              80 Start watching this issue

                Dates

                Created:
                Updated: