Are deployed issues counted as completed, thereby skewing the velocity for a sprint?

In JIRA, my team's velocity does not match what I'm seeing my team do. Specifically, the completed work is quite low while the committed work is quite high. Could this be due to deployed issues? Are those issues not counting as completed, thereby skewing the velocity? I'm also confused by what I'm seeing as committed issues. The report is showing a commitment amount nearly three times higher that what we agreed on in our sprint planning session.

1 answer

0 vote

Depends on how your board is configured. Irrespective of individual statuses, report counts the issues in the far right column, on the board, as completed. You can have one or more statuses mapped to this column.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

133 views 0 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you