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

    • 1
    • Severity 2 - Major
    • No

      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

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

          Form Name

            [JIRAALIGN-3945] Already resolved story in Jira when synced, returns wrong 'State' via API

            backbone-sync-bot made changes -
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Kyle Foreman made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]

            Kyle Foreman added a comment -

            Hi,

            This issue is fixed in the Jira Align 10.117.0 release.

            -Kyle

            Kyle Foreman added a comment - Hi, This issue is fixed in the Jira Align 10.117.0 release. -Kyle
            Khrystyna Mandziy (Inactive) made changes -
            Fix Version/s New: 10.117.0 [ 104693 ]
            backbone-sync-bot made changes -
            Status Original: In Review [ 10051 ] New: Waiting for Release [ 12075 ]
            backbone-sync-bot made changes -
            Status Original: In Progress [ 3 ] New: In Review [ 10051 ]
            Kyle Foreman made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 718870 ]
            backbone-sync-bot made changes -
            Status Original: Short Term Backlog [ 12074 ] New: In Progress [ 3 ]
            backbone-sync-bot made changes -
            Status Original: Long Term Backlog [ 12073 ] New: Short Term Backlog [ 12074 ]
            Kyle Foreman made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 715837 ]

              njones3@atlassian.com Nathan Jones (Inactive)
              e992016a60b0 Vishwajit Vinchurkar
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: