Transitioning Jira issues does not retain default/current values for certain fields

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      When transitioning a Jira issue from Crucible, Crucible does not retain the default or selected field values for custom select list (single line) fields.

      Steps to Reproduce

      1. In Jira, create an issue transition screen for moving an issue to a particular status (such as "Done")
        • On this screen, include a custom field of type "select list (single choice)" with multiple possible values. For this example, the possible values are "option 1", "option 2" and "option 3"
      2. Create an issue in Jira containing this custom field, and then edit the issue to give the issue a value of "option 2" for this custom field.
      3. Back in Crucible, on an open review - link the newly created Jira issue to this review
      4. Click on the linked issue in Crucible, and attempt to transition the issue (in this case to "Done")

      Expected Results

      In the modal window, the custom field should reflect the current value as it exists within the Jira ticket.

      Actual Results

      The custom field value of "option 1" is the first in the list.

      Crucible:

      Jira:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Notes

      This issue looks to be related to the jira-integration-plugin version currently used by Fisheye/Crucible, which is 3.0.4. A fix for this behavior was introduced in jira-integration-plugin 6.1.0 and higher.

              Assignee:
              Unassigned
              Reporter:
              Evan Slaughter (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: