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

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 43
    • 6
    • 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

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-76745 Missing information about "Split Issue" functionality on DC documentation

          • Low - Low priority issues
          • Needs Triage

          Suggestion - JSWCLOUD-23838 Save the custom field details when using Split issue feature in Backlog

          • Gathering Interest
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              mgocevska Maja (Inactive)
              Votes:
              252 Vote for this issue
              Watchers:
              128 Start watching this issue

              Dates

                Created:
                Updated: