Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Velocity Chart is not working as expected

Spruha Shah December 29, 2022

Sprint 4 is related to the board and the velocity chart still hides it after "Hide Unrelated Sprint" is turned on. Also, the completed green bar is not correct.

We checked the board filter and all the board configuration but couldnt find anything that would cause this. 

The velocity chart on each of the boards in showing incorrect information. 

Please check the attached images.hide unrelated sprint is on.pnghide unrelated sprint is off.png

 

2 answers

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 29, 2022

Welcome to the Atlassian Community!

Could you explain what you think is wrong with these reports?  (Other than showing that your team is not delivering what it should be)

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 29, 2022

Hi @Spruha Shah -- Welcome to the Atlassian Community!

First thing, I am using the cloud not server version, and so basing my suggestion on the documentation.

Have you check from which board the sprint was created?  When enabled, that option only shows the sprints created from the board which you are currently viewing.

https://confluence.atlassian.com/jirakb/how-the-hide-unrelated-sprints-feature-works-on-a-velocity-chart-in-jira-1082273005.html

Regarding the completed work, have you confirmed the issues were in a status which is mapped to the right-most column on the board?  That is how Jira Scrum boards determine "done" for a sprint.

Kind regards,
Bill

Spruha Shah December 30, 2022

Thank you for your response. 

I am not sure how, but the issue is fixed now. 

Suggest an answer

Log in or Sign up to answer