Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-9044

Specifying "Sprint" from JIRA ticket does not update it's Ranking

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Medium Medium
    • None
    • None

      This means that when you update Sprint field from JIRA - Ranking is not updated - thus sorting by ranking no longer shows all items in the current sprint at the top. This affects all user's To Do filters and subscriptions (as these are sorted by Rank) meaning that they may skip something important.

            [JSWCLOUD-9044] Specifying "Sprint" from JIRA ticket does not update it's Ranking

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JSWCLOUD Bug Workflow [ 3191766 ] New: JAC Bug Workflow v3 [ 3473812 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1879139 ] New: JSWCLOUD Bug Workflow [ 3191766 ]
            vkharisma made changes -
            Project Import New: Sun Apr 02 01:01:23 UTC 2017 [ 1491094883663 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 908367 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548381 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 746436 ] New: JIRA Bug Workflow w Kanban v6 [ 908367 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 534093 ] New: GreenHopper Kanban Workflow 20141014 [ 746436 ]
            Peter Obara made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            You are correct, updating the Sprint field does not change an issue's rank. However, this is by design. If you would like to update rank as well as add to a Sprint, you can drag the issue in Plan Mode.

            Peter Obara added a comment - You are correct, updating the Sprint field does not change an issue's rank. However, this is by design. If you would like to update rank as well as add to a Sprint, you can drag the issue in Plan Mode.
            Roman created issue -

              Unassigned Unassigned
              63a7223e2adf Roman
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: