Frequently Asked Questions (FAQ)
Below are some of the most common questions about configuring and using Jira Capacity Planner.
Q: Why does my users' availability or capacity appear as zero, even though I have configured the work schedule?
A: This commonly happens for two reasons. First, verify that in the Work Profile section, the "Start Date" and "End Date" fields for issues are correctly mapped. If these are not configured, the planner cannot calculate the workload. Second, ensure that the user has a dedication assigned (greater than 0%) in at least one team.
Q: A cell in the planner appears red, what does that mean and how do I fix it?
A: The red color indicates over-allocation: the work hours assigned to that user for that day exceed their available capacity. To fix this, hover over the red cell. The tooltip will show you the keys of the assigned issues. You can then proceed to reassign one of those issues or adjust their dates to redistribute the workload.
Q: I can't add a user to a team, the system won't let me, why is that?
A: The system has a validation to prevent a user's total dedication from exceeding 100% across all the teams they belong to. If you cannot add a user, it means their capacity is already fully allocated. You will need to reduce their dedication percentage in another team to free up their capacity and add them to a new one.
Q: I enabled a project in the settings, but a user who is a member of the project can't see the "Capacity Planner" tab, why?
A: The visibility of the tab depends on two conditions: 1) that the project is in the "Enabled Projects" list, and 2) that the user has the Jira permission to "Browse Projects". Check the project's permission schemes to ensure the user has this permission.
Q: When should I use a Global type team instead of a Project type team?
A: Use a Global team for cross-functional groups that do not belong to a single project, such as "Human Resources" or "UX/UI Design," as they will be visible in all enabled projects. Use a Project team for specific work squads (e.g., a Scrum team) that only operate within the context of one or more specific projects.