Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-3945

Already resolved story in Jira when synced, returns wrong 'State' via API

    XMLWordPrintable

Details

    • 1
    • Severity 2 - Major
    • No

    Description

      Issue Summary

      Already resolved story in Jira when synced, returns wrong 'State' via API.

      Steps to Reproduce

      1. Story is already resolved in Jira before sync with Jira Align
      2. In Jira Align State Mapping - 
        1. The resolved status is not mapped to any of the states 
          OR
        2. Jira resolved status is mapped to either of Jira Align states except '4 - Test Complete'
      3. in Jira Align, Accepted Date is mapped to resolutiondate
      4. UI shows the story is 'Accepted'
      5. Story API response does not show the state as 5 which is for Accepted

      Expected Results

      The story API response for state is consistent with the state shown in UI. 

      Actual Results

      The story API response for state is different and not consistent with UI. It could be any value other than '5' which is for Accepted. 

      Workaround

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

      Attachments

        1. resolutionDate setting.png
          resolutionDate setting.png
          114 kB
        2. Jira Align and Jira work item details.png
          Jira Align and Jira work item details.png
          296 kB
        3. State mapping.png
          State mapping.png
          111 kB
        4. Story_API_response.json
          0.9 kB

        Issue Links

          Activity

            People

              njones3@atlassian.com Nathan Jones (Inactive)
              e992016a60b0 Vishwajit Vinchurkar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync