The Sprint Marker Migration described at https://confluence.atlassian.com/display/AGILE/Sprint+Marker+Migration has an error when it recognizes whether there are Boards that need migration.

      We had a Scrumboard that matches the criteria

      (SPRINT_MARKERS_MIGRATED <> true or SPRINT_MARKERS_MIGRATED is null) and SPRINTS_ENABLED = true

      but the board was deleted.

      So there was no way to get the warning away except of hiding it which is bad as you then are not sure whether all boards that need migration are actually migrated. (Besides it would be handy to see the list of boards that still need migration, at least as Administrator if there are security concerns.)

      I worked around this by setting sprints_enabled to false in the database directly. After this the message was gone as it was the last board that Agile thought needs migration.

            [JSWSERVER-10090] Sprint Marker Migration needed check is erroneous

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.03
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2851974 ] New: JAC Bug Workflow v3 [ 2936966 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545896 ] New: JAC Bug Workflow v2 [ 2851974 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549308 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545896 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 908875 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549308 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747213 ] New: JIRA Bug Workflow w Kanban v6 [ 908875 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 584188 ] New: GreenHopper Kanban Workflow 20141014 [ 747213 ]

            User experienced this on this ticket: https://support.atlassian.com/browse/GHS-11061 (Agile 6.3.4)

            Steps to reproduce according to him:
            To reproduce It would be have an instance of Agile before the migration, create a scrum board with sprints, delete the board and then upgrade agile to a version that requires the migration, and you should still see the removed boards in the table.

            I will try to reproduce locally.

            Benito Picarelli added a comment - User experienced this on this ticket: https://support.atlassian.com/browse/GHS-11061 (Agile 6.3.4) Steps to reproduce according to him: To reproduce It would be have an instance of Agile before the migration, create a scrum board with sprints, delete the board and then upgrade agile to a version that requires the migration, and you should still see the removed boards in the table. I will try to reproduce locally.
            Michael Tokar made changes -
            Resolution New: Support Request [ 18 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              d3bc0f8a136c Björn Schwerdtfeger
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: