Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14869

Higher Ranked Sprint Should Have Higher Ranked Issues

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Problem Definition

      When we move an issue from backlog to an empty sprint, the RANK is not updated.
      Steps to reproduce:

      1. Create a new board with 2 sprints
      2. Create at least 3 issues to backlog
      3. Move Issue 1 to Sprint 2
      4. Move Issue 2 to Sprint 1
      5. Move Issue 3 to Sprint 2 after Issue 1
      6. On Search for issues page, you will notice the order of the issues is
        • Issue 1 -> Issue 3 -> Issue 2

      This is not sensible where the higher ranked sprint has a lower ranked issues.

      Note

      Noticed that this behaviour is caused by the act of moving an issue into an empty sprint is not changing the rank. When there's an issue in the sprint, the rank will then changed accordingly so the issues in the same sprint would have a similar rank.
      See Unable to embed resource: RANK.webm of type video/webm

      Suggested Resolution

      RANK should adjust according to the sprint even the sprint is empty.

      Attachments

        1. RANK.webm
          2.65 MB
        2. Screenshot1.jpeg
          Screenshot1.jpeg
          45 kB
        3. Screenshot2.jpeg
          Screenshot2.jpeg
          59 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cteh Ting (Chiou Ting Teh)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: