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

Resolved Date/Time is reset every time a transition screen shows the field

    XMLWordPrintable

Details

    Description

      Ever since the 'Resolved Date' was added to JIRA it is set every time there is a workflow transition using a workflow transition screen that contains the field.

      This is a pretty big problem for project reporting.

      Most workflows have some kind of 'Verify' state after the 'In Progress', or 'Working' state. When QA goes to qa and close the issue often the 'resolution screen' is used even though the resolution, often times, is already set. Using the 'resolution screen' a second time during the workflow is common and allows QA to decide and mark the bug as unfixable, won't fix, cannot reproduce, etc.

      Previously, with 'Resolution Date', the field would only change values when the value was set initially or changed.

      Now the value is being reset every time a transition form displays the field, even if it isn't changed.

      I marked this as critical because there are lots of issues that aren't closed until long after they are resolved - resetting the resolution, or resolved date, every time the field is shown is wrong.

      Steps to Replicate

      1. Create a workflow using 'open', 'verify' and 'closed' statuses
      2. On the transition from open to verify use the 'resolved issue screen' as the transition form
      3. On the transition from verify to closed use the 'resolved issue screen' as the transition form
      4. Create an issue
      5. Transition it to verify, set the resolution
      6. Note the date/time of the resolved date
      7. Wait 5 minutes (or just one, depending on your patience level)
      8. Transition from verify to closed, not touching the resolution
      9. Note the 'new' date/time for the resolved date. This shouldn't happen

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              a09a4d781816 William Crighton [CCC]
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: