Forums

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

There are no available sprints for this board - Velocity chart

Joanna Kalantzea April 7, 2020

I have created a separate Jira board for my two teams. They have the exact queries since they are part of the same project. However, for one of my teams, I cannot see the Velocity chart (message "There are no available sprints for this board " is displayed) although I can see all the other reports. Before starting the Sprint, we had all the backlog items ready for the new Sprint in the Product Backlog so no new issues were added after the Sprint started. I should also mention that this was not their first Sprint, they just didn't have their own separate Team Board. Any ideas on how can I resolve this?

 

Cheers!

2 answers

1 accepted

0 votes
Answer accepted
Ste Wright
Community Champion
April 12, 2020

Hi @Joanna Kalantzea

Is this a recent split into two boards?

Whilst the team might have had sprints before (if the two teams worked from the one board) - it depends if the issues in the current filter have been a part of the previous sprints - or if you've filtered those out.

The new board will only visualise sprints if previously sprinted issues are part of the filter.

Perhaps provide a screenshot of each filter if you need further assistance :)

Ste

Joanna Kalantzea April 23, 2020

Hi @Ste Wright !

 

Thank you very much for your reply! It seems it was needed for the Sprint to close properly before opening the new Sprint in order to have access to the Velocity Chart. Finally I can see it!

Like # people like this
Sobiya Momin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2020

@Joanna Kalantzea  

What did you mean by  * needed for the Sprint to close properly before opening the new Sprint*?

 

Yes I stil have the issue & Sprints are properly closed & started.

0 votes
Joanna Kalantzea May 22, 2020

Hello @Sobiya Momin !

By closing it properly I mean that firstly the previous Sprint should be closed and afterwards open the new one.

Also I have observed that the Board for my team was opened initially as a Kanban board and changed it into Scrum board later. This is one of the other reasons the board could not show me the Velocity chart. So I had to wait another Sprint to be closed on the board as a Scrum board. Hope this information is useful for you.

 

Cheers,

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events