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

Error "No issues present in sprint to generate scope change model" when viewing the Velocity Chart

XMLWordPrintable

      As mentioned here:
      https://confluence.atlassian.com/display/GH/Viewing+the+Velocity+Chart?focusedCommentId=317948993#comment-317948993
      the problem appears also in case of our instance, in a board with default, consecutive sprint names (Sprint 76, Sprint 77 etc).
      The suggested workaround:
      https://confluence.atlassian.com/display/GH/Viewing+the+Velocity+Chart?focusedCommentId=317950207#comment-317950207
      helped just once but seems not to work anymore.

            [JSWSERVER-7250] Error "No issues present in sprint to generate scope change model" when viewing the Velocity Chart

            rpayton added a comment -

            How can I view the newly created Atlassian Support tickets? The links say I need to Authenticate to see more information, but the link just takes me to the support home. The three tickets I cannot view:

            GHS-6972
            GHS-6971
            https://extranet.atlassian.com/pages/viewpage.action?pageId=2221328895

            rpayton added a comment - How can I view the newly created Atlassian Support tickets? The links say I need to Authenticate to see more information, but the link just takes me to the support home. The three tickets I cannot view: GHS-6972 GHS-6971 https://extranet.atlassian.com/pages/viewpage.action?pageId=2221328895

            Brandon Barlow added a comment -

            We're also seeing this in JIRA 6.2.2 / JIRA Agile 6.3.12 . It seems to be related to sharing projects across multiple Scrum boards, but we have been unable to reproduce as of yet.

            Brandon Barlow added a comment - We're also seeing this in JIRA 6.2.2 / JIRA Agile 6.3.12 . It seems to be related to sharing projects across multiple Scrum boards, but we have been unable to reproduce as of yet.

            Mark Love added a comment -

            We're also getting the same message. It came up with the MD when he asked me to show the team's velocity. Very embarrassing.

            We have been moving issues between teams / boards but I don't know why this should cause it to break like this.

            Mark Love added a comment - We're also getting the same message. It came up with the MD when he asked me to show the team's velocity. Very embarrassing. We have been moving issues between teams / boards but I don't know why this should cause it to break like this.

            Peter Callies added a comment -

            In what way did Support resolve this?

            Peter Callies added a comment - In what way did Support resolve this?

            Toivo Vaje added a comment -

            Same problem. Seems that if there's a issue from team A that has been assigned for another team B only for a while and assigned back to the original team before closing, there's a problem. Team A's Sprint will be shown in Team B's reports, but since there's no issues completed, there's a problem.

            Toivo Vaje added a comment - Same problem. Seems that if there's a issue from team A that has been assigned for another team B only for a while and assigned back to the original team before closing, there's a problem. Team A's Sprint will be shown in Team B's reports, but since there's no issues completed, there's a problem.

            beck added a comment -

            We are seeing a similar issue as well...

            Note from my engineers:
            "For last few sprints, we noticed that velocity reports is not working – throwing error for CorePerformance, & Carbonite boards.
            Is there any setting we need to do?"

            beck added a comment - We are seeing a similar issue as well... Note from my engineers: "For last few sprints, we noticed that velocity reports is not working – throwing error for CorePerformance, & Carbonite boards. Is there any setting we need to do?"

            Kevin Dalton added a comment -

            I am getting the same error and it is because we have a sprint that was closed with no issues.

            Kevin Dalton added a comment - I am getting the same error and it is because we have a sprint that was closed with no issues.

            rbn added a comment -

            I am getting the same error on my project. I have some overlapping sprints since we have multiple teams for the same project.

            The same thing is observed at our site.

            rbn added a comment - I am getting the same error on my project. I have some overlapping sprints since we have multiple teams for the same project. The same thing is observed at our site.

            Joshua Deixler added a comment -

            I am getting the same error on my project. I have some overlapping sprints since we have multiple teams for the same project.

            Joshua Deixler added a comment - I am getting the same error on my project. I have some overlapping sprints since we have multiple teams for the same project.

            RenjithA added a comment -

            Hi,

            I have moved this issue to be handled under Atlassian Support and you can access the new issue created in the linked issues section.

            We will provide you with our response in the new issue created. I am proceeding to close this issue.

            Cheers,
            Renjith

            RenjithA added a comment - Hi, I have moved this issue to be handled under Atlassian Support and you can access the new issue created in the linked issues section. We will provide you with our response in the new issue created. I am proceeding to close this issue. Cheers, Renjith

              Unassigned Unassigned
              394e0685c201 Piotr Polak
              Affected customers:
              0 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: