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

Regression: "Clone Issue" action Clones Original Estimate field value

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 5.2.4, 5.2.4.1, 5.2.5, 6.0.5, 6.0.6, 7.1.9
    • Issue - Actions

    Description

      According to the Cloning an Issue documentation:

      Things that aren't cloned:

      • Time tracking
      • Comments
      • Issue history

      However, after testing this on the latest JIRA 6.0.6, the Original Estimate field gets copied when the issue is cloned:

      Original Issue

      Cloned Issue

      The fix in Clone issue should not clone the Original Estimate, Remaining Estimate, and Time Spent fields was to copy only Original Estimate value to the clone.

      Attachments

        1. clone_1.JPG
          clone_1.JPG
          251 kB
        2. clone_2.JPG
          clone_2.JPG
          246 kB

        Issue Links

          is a regression of

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-7165 Clone issue should not clone the Original Estimate, Remaining Estimate, and Time Spent fields

          • Medium - Medium priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-63398 Clone Issue Copies Time Tracking Incorrectly

          • Low - Low priority issues
          • Gathering Impact

          Activity

            People

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated: