Velocity charts and burndown charts

[Daban Babaker]

Hi,

In our team sprints, we add epics and corresponding user stories etc that we are committing to work on during that sprint, however, when viewing the velocity and burn down chart we can see that the committed story points are much higher than the completed story points for that sprint. 

I've found that this is because it is adding all the story points from every issue type we've added, we only want the story points for user story issue types to be considered and not the epic issue type when the points are being shown in the velocity and burndown chart. 

is there a way to change the velocity and burndown charts to show story points for only user story issue types?

[Stephen_Lugton]

Hi @Daban Babaker 

The simple answer is not to add epics to the sprint.

The work being done is described in user stories or tasks.

Story points are used to provide an estimate for effort or complexity of the work being done for each user story or task.

Sprints are a way of committing to a certain amount of work in a certain time period, and tracking completion of that work.

Since user stories and task represent work they are what should be in the sprint, and the story points assigned to completed user stories or tasks define the sprint velocity.

Epics on the other hand are ways of grouping the work and don't actually represent work by themselves, so they should not be in the sprint.

[Alexey Pavlenko _App Developer_]

Hi @Daban Babaker ,

Natively, unfortunately, it's impossible to achieve, however with the app I developed - Multi-team Scrum Metrics & Retrospective you can achieve it via custom JQL metrics.

Also, you can see several sprints/months/quarters/half-years/years and several boards/teams in a single view, coduct in-place retrospections and much more.

Best regards,
Alexey