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

Backlog Ranking: JA Feature ranking is not completely pushed to Jira

    XMLWordPrintable

Details

    • 2
    • Severity 3 - Minor
    • No

    Description

      Issue Summary

      Pushing rank to an external system doesn't completely reflect the ranking set if an error occurs midway.

      Steps to Reproduce

      1. Create 10 JA features synced with Jira (Epics)
      2. Set the T1 filter to Program (Based on the features created)
      3. Navigate to Backlog > Feature backlog
      4. Rank the features and push the rank to an external system.
      5. Wait for it to sync and check that the ranking is reflected in Jira.
      6. Now, remove/delete one of the synced features in Jira. (somewhere in between)
      7. Navigate back to JA backlog and re-arrange the ranking
      8. Push this new feature backlog ranking to Jira.
      9. Wait for it to sync and check the results in Jira

      Expected Results

      Rankings in Jira should match Jira Align.

      Actual Results

      Some Jira epics are not ranked based on what we see in JA Feature backlog.

      An error is also captured in Splunk during push rank:

            JsonErrorMessages: The issue no longer exists.
             RequestBody: {"issueKeys" :["PRJA-2968"], "rankAfterKey":"PRJA-4238","customFieldId":12630  }
      

      Workaround

      Make sure that the corresponding JA Feature of the removed/deleted Jira Epic is also removed/cancelled/deleted in Jira Align.

      Attachments

        Issue Links

          Activity

            People

              pkreidenkov@atlassian.com Pavlo Kreidenkov
              lsoronio@atlassian.com Leo Soronio
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync