Getting started with Capacity Tracker
After successful installation, you will be able to see “Capacity Tracker” icon on the left-hand side panel in JIRA. Please refer following step by step guide to start working with Capacity Tracker.
- 1.1 Step 1: Go to Capacity Tracker
- 1.2 Step 2: Select iteration and start with configurations
- 1.3 Step3: Set up appropriate permissions in order to edit configurations.
- 1.4 Step 4: Add or import users for tracking.
- 1.5 Step 5: Setup member configuration
- 1.6 Step 6: Setup board configurations.
- 1.7 Step 7: Review the Capacity Tracker details
- 2 Edge cases and notes
Step 1: Go to Capacity Tracker
Step 2: Select iteration and start with configurations
If you have single iteration (sprint/version) then it will be pre selected to get started. If you have multiple of those in the board then select the most recent or active iteration and start configuring it.
Step3: Set up appropriate permissions in order to edit configurations.
This step is applicable only if your Jira administrator has enabled Capacity Tracker’s Jira permission control. Please reach out to your Jira administrator in order to get write access.
If Jira permission control is disabled or you already have appropriate permission granted, you will not see an error message and instead you will be able to click on “Edit“ and navigate to configuration page. For more details on permissions refer here https://inprowiser.atlassian.net/wiki/x/AQBAE
Step 4: Add or import users for tracking.
Any users with work allocation in the selected sprint will be detected by Capacity Tracker and will be listed under “View“ option. Alternatively, you can search, select and add users from the add user drop down menu.
View and Import users
Search and Add users
Step 5: Setup member configuration
Once team members are added, you can do the following:
Assign role: you can select predefined roles or you can create custom roles.
Define team members working days.
Add Days off the team members.
Configure their daily capacity. (Note: If the capacity type is selected as hours then the daily capacity will be represented as hrs/day, if the capacity type is selected as Story Points then the daily capacity will be represented as StoryPoints/day.
Step 6: Setup board configurations.
These configurations are global settings for the board. They apply to all iterations (sprints/versions) in the selected project board.
Choose the capacity type as per your project needs and working practices. Ensure that they are aligned with your project and team’s estimations practices.
Configure default working days for the entire team according to your needs for the project board.
Add team holidays to account for general unavailability of team members for the selected iteration.
Save & Close after all configurations are set. You will be redirected to the Capacity Tracker list page.
Step 7: Review the Capacity Tracker details
Check out capacity tracking details. This graphs indicates how much is the work allocation (hours/story points) for the unit availability (hours/story points).
Please ensure Jira’s default time tracking feature is enabled. Estimation fields are configures in your project schemes and screens. Jira’s default Remaining Estimate field is used to estimate and track the remaining work.
Edge cases and notes
Here are some edge cases that may prevents Capacity Tracker from working as intended and as a result you will not be able to view team capacity and workload bar charts as expected.
If team members are not added and configured for the iteration.
If your iteration/board is blank/empty. i.e. You don’t have any stories or sub-tasks in it.
If you have not allocated the stories and sub-tasks to team members.
If you have not used the remaining estimate field to estimate the stories and sub-tasks of your project while your capacity type configured for hours based tracking.
If you have not used the default story points to size the stories in your project while your capacity type is configured for story points based tracking.
If you are working on a future iteration, but you haven’t configured start and end date.
If you are using custom fields for estimations.