Hi Jira gurus,
I need your help with making Jira to include bug estimates in velocity reports.
We are using Jira cloud. I've added Story Point Estimate field to the Scrum Bug screen. When I create bugs I can see and enter the estimation field. But the estimation is not counted in the velocity or current sprint size reports.
There are many bugs that get assigned to the sprint during sprint planning. Without bug estimations included in reports, it looks like the team delivers less work at the end of sprint. For example, let's say our velocity is 72 points. We take on user stories worth of 50 points, and 5 bugs each estimated at 4 points. You'd think the sprint size would say 70, but it doesn't - it says 50.
How could I fix it?
Hello Elvin,
By default, Story points context is only applicable for Story and Task issue type. To allow story points to be applicable to bugs, the following steps must be performed:
1 - Configure your Story contexts to be applicable to Bugs:
- Navigate to JIRA settings > Issues > Custom Fields
- Find the Story Points and click on Configure
- Click on Edit Configurations and select the Bug issue type under the Choose applicable issue types menu
2 - Add the Story Points to the bug screens
- Navigate to your project > Project Settings > Screens
- Add the Story points to the bug screens (Create/View/Edit)
For more information about this, check the documentation below:
- Configuring Estimation and Tracking
Let me know if this information helps, Elvin.
Hi Petterson,
Thanks for taking the time. I followed your instructions, but still confused a bit and need your help.
Firstly I followed step 1 and added story points to bugs.
Next, I navigated to the screens and wanted to add story points to the bug screen. But there are 2 of them: Story points and Story point estimates. I don't know which one to use. When I add both, both show up on bug view.
I wanted to see which one I used on the Story screen, but I couldn't see any of them on the story screen, although we are currently adding story points to stories and it shows up in reports. I am so confused. Could you please clarify?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Elvin,
The field "Story Point Estimate" is a Jira default field. This field belongs to the project template "Next-Gen" (also known as Agility).
The main difference between this field and the field "Story points" is that the "Story points" field (a field which belongs to the "classic" projects) allows you to edit its context, while "Story Point Estimate" is locked.
That been said, for a classic project, I recommend you to use the "Story points" field.
About the story points displaying in the issue view, it should be displaying properly in the old issue view if it has a valid value added to it:
I recommend you to check the following:
- Navigate to project > Project Settings > Fields > Check if the Story Points is not hidden on your project
- When creating the Story, make sure you have properly configured a valid value for the Story Points field
We will be waiting for your answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I decided to record my screen instead to avoid any confusions. Would you please take a look and see what is happening?
The link: https://drive.google.com/file/d/1EaPUTIHgYAKOHJwKWty7AUAJWQXE_QT_/view?usp=sharing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Petterson,
Did you have a chance to watch the video? I am confused as to what happens if I stop using Story Point Estimates and start using Story Points.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My guess is that your bugs are sub-tasks under stories? Sub-task estimates do not count towards velocity, as the estimates and commitment is done at the story level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.