Usage and admin help
Are you on the right help page?
The following information only applies to next-gen projects.
To check which type project you need help with, look at the bottom of your project’s left-hand sidebar:
If you see an icon stating You’re in a next-gen project with Give feedback and Learn more menu items, you're in a next-gen project.
If you don't, you're in a classic project. Check out our classic project documentation.
Calculate your team's velocity by estimating each issue in your backlog. Currently, only story point estimation is available for next-gen Software projects but we'll add other estimation methods in the coming months.
Enable estimation for your next-gen project
Navigate to your next-gen software project.
Go to Project Settings > Features.
Enable or disable the Estimation feature.
If you’re a Jira admin
When you navigate to the issue type configuration screen, you might notice that there will now be two Story point estimate fields when you do this. This is because one is for classic Scrum/Kanban projects, and the other is for next-gen Scrum/Kanban projects.
Add estimates to epic issue types
When you enable the Estimation feature, the Story point estimate field will be available to all standard-level issues types. You can also add this field to epic issue types if you want to estimate epics. Check out Customizing an issue's fields in next-gen projects for more information.
How to estimate issues
To estimate an issue:
Select an issue on either the board or backlog.
In the issue detail view, under Story point estimate, enter a valid estimate. Story point estimates must be numerical, but can include decimal points.
This field is available wherever you can open an issue, including on the Backlog, on the Board, and on the Roadmap (if you've added the Story point estimate field to epic issue types).
View estimates in reports
The estimates entered on your project's issues will affect your project's reports. Check out the Reports page for more information.
Estimation takes place in the backlog. Read more about maintaining a healthy, well-organized backlog.
Was this helpful?