nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is a bug counted towards velocity in Jira?

Jim Stewart_1wcyht

Question – if the team finishes two stories at five points apiece plus one bug fix (discovered during sprint) worth three points, is the velocity of the team 10 (based on stories) or 13 (since the bug is a story of sorts.)? I looked into this a little bit and there was no consensus. I'm going to assume you don't as a new Bug Issue has no estimate. But it's an interesting real-world question as well.

Accepted answers

Nic Brough -Adaptavist-

13 will be counted because that's what you recorded.

Generally, you should not be doing this though - when you estimate a story, you are kind of expected to include some allowance for bugs being found and fixed as part of the story.

All comments

Nic Brough -Adaptavist-

13 will be counted because that's what you recorded.

Generally, you should not be doing this though - when you estimate a story, you are kind of expected to include some allowance for bugs being found and fixed as part of the story.

Jim Stewart_1wcyht

I don't disagree with that philosophy at all. You may (or may not) be surprised at the divergence of opinion on this. Thanks.

REMAXUser

If the bug were directly part of one of the two 5-point stories, we would not count it as a new story or add'l points - as @Nic said above - that should be considered in the original story, and is (in my opinion) not a bug, as it wasn't released.

If the bug were an unrelated and separate use case for code that has been merged, then it should be pointed and added to the velocity count).

^ Opinion only^

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud