-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
6.3.0.2
-
None
-
6.03
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Steps to reproduce
- create a Planned Sprint;
- add Issues to the new Sprint;
- add or edit Story Points in those Issues;
- start the Sprint.
Expected result
The Story Points values existing at the moment the Sprint was started are accounted for in all reports.
Actual result
Sprint Report displays no Story Points ( - ) for Issues that had the value changed after they were added to a Planned Sprint, but before it was started. Burndown Chart shows correct values.
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
- mentioned in
-
Page Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-9790] Sprint Report does not include Story Points added to a Planned Sprint
This bug is resolved with the 6.3.2 version. our system is running JIRA Agile (v6.3.2.1) and Atlassian JIRA (v6.0.6#6105-sha1:9713ad1) but we aren't seeing this resolution. Do we know when this will be pushed out and available for update?
pierre.carlier
added a comment - +1. It's a duplicate of GHS-8169 . Good that it's fixed ! 
volodymyr.koval
added a comment - Thanks a lot for the good news! The problem lies in the calculation of the data for the report, not the storage of the data. Thus the fix will also fix any existing reports.
volodymyr.koval
added a comment - We ran into this issue also. Can someone clarify if the broken sprints will get fixed with the JIRA Agile update? To me here "broken" means the wrong velocities calculation in the affected sprints.
volodymyr.koval
added a comment - We ran into this issue also. Can someone clarify if the broken sprints will get fixed with the JIRA Agile update? To me here "broken" means the wrong velocities calculation in the affected sprints. 
François St-Amant
added a comment - Also, if you add an issue to a new sprint and close this issue (i.e. as duplicate), it will no longer appear in the list before the sprint starts but will be visible in all JIRA Agile views after the sprint has started. Seems like any change to an included story before the sprint starts is ignored in the Sprint Report.
François St-Amant
added a comment - Also, if you add an issue to a new sprint and close this issue (i.e. as duplicate), it will no longer appear in the list before the sprint starts but will be visible in all JIRA Agile views after the sprint has started. Seems like any change to an included story before the sprint starts is ignored in the Sprint Report. 
Steve Mullin
added a comment - Same issue here. 
frank yang
added a comment - I have the same issue here.
I started print on 8/27 with story points and completed the sprint on 9/10.
The story points are missing the sprint report shown as "-".
I created other sprints a few weeks ago and started one new sprint on 9/10, will these sprints have the same issue or not?
If yes, how can i avoid this from happening again?
frank yang
added a comment - I have the same issue here.
I started print on 8/27 with story points and completed the sprint on 9/10.
The story points are missing the sprint report shown as "-".
I created other sprints a few weeks ago and started one new sprint on 9/10, will these sprints have the same issue or not?
If yes, how can i avoid this from happening again?
gigado:
If you believe you're still seeing symptoms of this issue, it is best to contact support. You can log in with the same credentials that you use for this site. If you raise an issue there, we can look at your specific data in a secure fashion and get to the bottom of the issue quickly.