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

[JIRAALIGN-1251] Sprints: User is not informed that when moving Sprint from one PI to another Sprint is mapped to very first Anchor from new PI

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Medium
    • 10.68
    • 10.65
    • team - sprints
    • None
    • 1
    • Severity 3 - Minor
    • Stubborn Dragons - RHP8

    Description

      Issue Summary

      Sprints: User is not informed that when moving Sprint from one PI to another, the sprint is mapped to very first Anchor from new PI

      Steps to Reproduce

      1. Login
      2. Open any PI with Sprints.
      3. Open any Sprint in it
        #Reassign Sprint to different PI

      Expected Results

      Map the anchor to the date range that includes the sprint's end date, or to the Anchor that is closest to Sprint's End date

      Actual Results

      Sprint is mapped to First Anchor of the new PI

      Workaround

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

      Attachments

        Issue Links

          Activity

            People

              kforeman@atlassian.com Kyle Foreman
              rpetrunyak@atlassian.com Roman Petrunyak (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync