Comparing size visually always works much better than just seeing pure numbers. Currently in JIRA Software the sprint backlog estimation process works like this:
In Agile Estimate add-on we've tried to improve the way how teams work with sprint backlog estimation.
Check out Agile Estimate add-on on Atlassian Marketplace |
Users can start using Agile Estimate add-on with Scrum boards immediately after add-on installation without any additional configuration.
Kanban boards require "Time tracking" issue field on Edit issue screens for projects which are part of a Kanban board. |
When user changes time estimate of an issue on a Kanban board JIRA assumes/requires that "Original estimate" field can be edited via JIRA edit issue screen too. That's why you need to check if "Time tracking" field is part of Edit Issue screen.
If "Time Tracking" field is absent on "Edit Issue" screen then user will see an error message "Error updating issue estimate":
The easiest way to update your project edit issue screens is via "Project settings" → "Screens" tab:
Click on a screen for "Edit issue" and add "Time tracking" field to a screen if it is not yet there:
You should add "Time tracking" field to all issue types if they have different Issue Type Screen Schemes |
Changing estimates on Kanban board should now work fine:
Agile Estimate add-on shows a selected sprint backlog in dialog where all sprint backlog items have estimation slider.
Moving slider left/right dynamically changes and saves estimation for that issue.
Total number of issues in sprint and total estimation of all stories is also available.
All estimations are visually represented in the estimation bar so that users have visual representation of the estimation size and can compare backlog stories with each other and adjust them easily.
Agile Estimate add-on supports boards with both Story and Hours estimation types.
Please, contact us via the following support channels.
Please, read our Data Security and Privacy Statement for Atlassian Cloud add-ons.