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

Sprint Report showing story points in '-' (hyphen) values before sprint start

XMLWordPrintable

      As per quote from the documentation:

      Issues added after the sprint starts are indicated with an asterisk.

      After do some testing on our JIRA instance, please see the steps:

      1. Create a new Scrum board.
      2. Create two new issues (Story Points issue type).
      3. Create a new Sprint (do not start the sprint).
      4. Drag the Issues to the new Sprint (do not add any Story Points values).
      5. Then, edit the story estimate points to 10 for SCRUM-1 and SCRUM-2.
      6. Now, start the sprint and go navigate to the Sprint Report the values show '-', please see:

      Finding:

      • Its happen to all issue types as well.

        1. instance_result.JPG
          instance_result.JPG
          22 kB
        2. Screen Shot 2013-09-10 at 6.18.07 PM.png
          Screen Shot 2013-09-10 at 6.18.07 PM.png
          33 kB
        3. Sprint_Report.JPG
          Sprint_Report.JPG
          52 kB
        4. Sprint 3 Screen Capture.PNG
          Sprint 3 Screen Capture.PNG
          47 kB
        5. Sprint 4 Screen Capture.PNG
          Sprint 4 Screen Capture.PNG
          51 kB
        6. Sprint 5 Screen Capture.PNG
          Sprint 5 Screen Capture.PNG
          43 kB
        7. test_with_only_story_points.JPG
          test_with_only_story_points.JPG
          27 kB

            [JSWSERVER-9785] Sprint Report showing story points in '-' (hyphen) values before sprint start

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.03
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850170 ] New: JAC Bug Workflow v3 [ 2936430 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544979 ] New: JAC Bug Workflow v2 [ 2850170 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551716 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544979 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: future_sprints New: affects-server future_sprints
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909557 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551716 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 747046 ] New: JIRA Bug Workflow w Kanban v6 [ 909557 ]
            Nick Stemerdink made changes -
            Link New: This issue duplicates GHS-11334 [ GHS-11334 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 555262 ] New: GreenHopper Kanban Workflow 20141014 [ 747046 ]

            Chris Evans added a comment -

            We've had this same issue when re-estimating story point values for features which weren't completed (or started) during our sprint. When planning the new sprint we added the features that weren't completed, changed the estimates and then noticed the velocity chart had a lower commitment that completed. After changing the story point estimate back to the original value, the sprint report still shows '-'s in place of the esimate. Any news on a fix or workaround?

            Chris Evans added a comment - We've had this same issue when re-estimating story point values for features which weren't completed (or started) during our sprint. When planning the new sprint we added the features that weren't completed, changed the estimates and then noticed the velocity chart had a lower commitment that completed. After changing the story point estimate back to the original value, the sprint report still shows '-'s in place of the esimate. Any news on a fix or workaround?

              Unassigned Unassigned
              ckimloong John Chin
              Affected customers:
              0 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: