There's a huge variety of ways to estimate stories, but the objective of every approach is to be able to get better at predicting how much work the team can do each sprint. In agile scrum, this translates to knowing the team's velocity.
Velocity measures the number of 'estimation units' that a team usually completes from sprint to sprint. It is effectively a productivity rate based on an estimation of volume of work, and it is best worked out in a measure other than 'time'.
Estimate in points, track in time
Even when you estimate in story points, you can still track in time if you want. Knowing the team velocity (regardless of the measure used) enables you to roughly guess how long estimated backlog items will take to complete.
But Jira Software does also have a couple of dedicated fields (Remaining Estimate and Time Spent) to track time while using story points.
NOTE: You need to be a board admin to make any configuration changes to a board. If you created the board, then you're already the admin.
Go to Board > Configure > Estimation.
- Select the Estimation Statistic (unit of estimation) - choose from story points, original time estimate, and issue count.
- Switch on the Remaining Estimate and Time Spent option to get a more accurate picture of how things are tracking in time units.
- If you leave Time Tracking as None, you can still refer to reports such as the Burndown chart to monitor progress.
Find out more about how time tracking work in projects in the configuring estimation and tracking topic.