Below Sprint Report is show correctly but in release burndown its showing wrong information. Still now my team has completed 28 story point but out of 28, 26 is showing in different sprint name (V_0.1_SPRINT-2) and 2 is showing in V_0.1_SPRINT-1 (My sprint). Please check below screen grab on urgent basis and let me know.
Of the 28 points, can you check each issue and see what sprints they are all in? There are no screenshots attached, so we're a little in the dark here.
Checked all issues all are showing in my sprint & Version also.Please find attachment with all description
The doc doesn't look right, the pictures are unreadable.
Could you give us a list of the issues and what sprints they are in? Issue navigator and search for "sprint in (both of the sprints)". Then give us just the columns issue key, sprint, status and story points (so you won't leak us any private data)
Has this been resolved? I'm having a similar issue. Our Q2 Release Burndown is showing Q3 sprints.
When i go into our Q3 Release Burndown, Sprint 1 is not listed, however Sprint 1 issues are included in Sprint 2 list of issues (this Release Burndown is saying we had 65 points for Sprint 2 - when in reality Sprint 1 was 40 and Sprint 2 was 25...which is correct and coming from the Sprint Report).
Hi , i also see a similar problem, in Release Burndown it shows an item under wrong sprint name. i have total 3 scrum teams working on the same product backlog and all run parallel sprints with start and end on same time.
Same issue using JIRA cloud here. If I view the issues in the issue navigator they show the correct sprint, however the EPIC burndown view puts them in an incorrect sprint and makes the graph useless. Seems to be a widespread isssue - any workarounds available (please do not suggest an addon)?
Was there any answer to this question? I am experiencing similar issues and looking for input.
has anybody received an answer for this bug? I see this as a major bug and makes burndown reporting for us un-usable.
Hi guys,
Are you planning to resolve this ticket?
Thanks
I am also seeing this exact issue, and got here because of a link in a different (closed) issue.
It really doesn't help to close a ticket and point to a place that really has no information.
Is there any update on this and can it be fixed?
It looks like you're new here. Sign in or register to get started.
