Error with speed graph

kalvarez
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!
March 22, 2024

When moving incidents between different boards, an error was generated in the speed graph and it did not show me the current sprint (running) on the board. With the moved incidents, the Sprints where they were were auto-generated. I deleted those sprints from the graph on the current board. but now it tells me there is no sprint to show? how would this be solved? I clarify that if I have the sprint status report metric and other metrics ok, it just doesn't show it in the velocity graph.image.png

1 answer

1 accepted

0 votes
Answer accepted
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 23, 2024

Hi @kalvarez and welcome to the Community!

I hope you don't mind I reply in English here ... I get from your description that you have moved issues from 1 board to another, which made sprints appear in that last board that were not there before and so you decided to delete those sprints from the board, which then broke the data in your velocity chart?

It is not clear to me how you moved the issues from one board into the other, but I am guessing you actually used the move function to do so.

Here is what may have happened: sprints are created from a board, but they are visible across your entire Jira. When you add issues to a sprint (from a board), you fill out that sprint as a value in the sprint custom field of that issue. When you then move that issue to another project, the select sprint still remains selected to that issue. That's the first thing to keep in mind.

Second: a board is essentially a set of features that shows the information of the issues selected by the board filter. It does not contain issues, it displays them and offers you some ways to organise them. And so, if you display issues on a board that are already linked to a sprint, that sprint automatically is displayed on your board as well (even if that sprint is coming from somewhere else in Jira). By deleting the sprint from the board, I suspect you have entirely deleted it from Jira, thus impacting your velocity chart. 

While I am not sure why you would want to move issues in an active sprint to a different board, if you would want to do a similar operation again in the future, don't delete the sprint itself, but edit the individual issues in your sprint and remove the sprint from the sprint field there instead. That way, the assignment of the issues into that sprint will be removed, but the sprint itself will not be impacted.

Hope this helps!

kalvarez
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!
March 25, 2024

Hello Walter, thank you for responding, if I take what you say as a lesson learned from what happened, I have to wait to close the Sprint to see if it takes the correct Sprint, otherwise I will have to apply an Excel in my records, greetings.

Suggest an answer

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

Atlassian Community Events