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

Sprint Marker Migration needed check is erroneous

XMLWordPrintable

      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

            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.

            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 added a comment -

            Bjoern1 if the board was deleted then there shouldn't be a row in the table corresponding to that board.

            I think this warrants further investigation by our Support Team. Would you please create a support ticket at http://support.atlassian.com?

            Michael Tokar added a comment - Bjoern1 if the board was deleted then there shouldn't be a row in the table corresponding to that board. I think this warrants further investigation by our Support Team. Would you please create a support ticket at http://support.atlassian.com ?

            Björn Schwerdtfeger added a comment -

            I didn't say anthing about caching.
            The point is that the board was deleted, even the owner was not able to view it with the help of the id I took from the database.
            But still the entry in the table AO_60DB71_RAPIDVIEW was there that made the check fail.
            And as soon as I changed the SPRINTS_ENABLED value for that board, the message was gone immediately.

            Björn Schwerdtfeger added a comment - I didn't say anthing about caching. The point is that the board was deleted, even the owner was not able to view it with the help of the id I took from the database. But still the entry in the table AO_60DB71_RAPIDVIEW was there that made the check fail. And as soon as I changed the SPRINTS_ENABLED value for that board, the message was gone immediately.

            Michael Tokar added a comment -

            The check for whether there are any boards that still need migration is not cached. If your board was deleted then it should not have been included in the results of the query.

            Michael Tokar added a comment - The check for whether there are any boards that still need migration is not cached. If your board was deleted then it should not have been included in the results of the query.

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

                Created:
                Updated:
                Resolved: