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

Velocity Report - No issues present in sprint to generate scope change model

    • Icon: Bug Bug
    • Resolution: Support Request
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • None
    • None

      We found that we have a Sprint what has no issues assigned to it but we are unable to remove it to resolve the issue.

            [JSWSERVER-9036] Velocity Report - No issues present in sprint to generate scope change model

            Hi,
            Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com).
            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Hi, Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com). Regards, JIRA Agile Team

            We have 1 team using the board and they closed an empty sprint which now causes this error. We have a team unable to use the velocity report because of this issue

            Kevin Dalton added a comment - We have 1 team using the board and they closed an empty sprint which now causes this error. We have a team unable to use the velocity report because of this issue

            We have 1 team using the board and they closed an empty sprint which now causes this error. We have a team unable to use the velocity report because of this issue

            Kevin Dalton added a comment - We have 1 team using the board and they closed an empty sprint which now causes this error. We have a team unable to use the velocity report because of this issue

            We had orphaned sub-tasks. A story was moved to a different team and the sub-tasks were still assigned to the first team.

            julie miyasato added a comment - We had orphaned sub-tasks. A story was moved to a different team and the sub-tasks were still assigned to the first team.

            We have 1 team using the board and they closed an empty sprint which now causes this error.

            Kevin Dalton added a comment - We have 1 team using the board and they closed an empty sprint which now causes this error.

            Hi Lalit. I did the export and reviewed and fixed the issues.

            There are currently no issues across teams/boards yet 2 boards are still producing this error.

            julie miyasato added a comment - Hi Lalit. I did the export and reviewed and fixed the issues. There are currently no issues across teams/boards yet 2 boards are still producing this error.

            That means still there are some issues which are assigned to cross teams.
            Best way to fix: Export all(open + closed sprints) issues to excel and filter them on Team column. Go over all the issues and fix those issues where sprint and team combination is not proper

            Lalit Singh added a comment - That means still there are some issues which are assigned to cross teams. Best way to fix: Export all(open + closed sprints) issues to excel and filter them on Team column. Go over all the issues and fix those issues where sprint and team combination is not proper

            @ Lalit - that is exactly what happened to us, on multiple boards. We have fixed the issues but sprints from one team is still showing on other boards and velocity reports are still producing the error.

            julie miyasato added a comment - @ Lalit - that is exactly what happened to us, on multiple boards. We have fixed the issues but sprints from one team is still showing on other boards and velocity reports are still producing the error.

            If there are multiple teams in the project, then make sure that the issues are not cross-assigned. for eg. A issue created in Team A's sprint (visible on Agile board of team A) is edited and assignment of Team is changed to Team B. In this scenario the velocity chart will break.

            Lalit Singh added a comment - If there are multiple teams in the project, then make sure that the issues are not cross-assigned. for eg. A issue created in Team A's sprint (visible on Agile board of team A) is edited and assignment of Team is changed to Team B. In this scenario the velocity chart will break.

            Is there anyway around this issue?

            Kevin Dalton added a comment - Is there anyway around this issue?

              Unassigned Unassigned
              kevin.dalton Kevin Dalton
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: