Here is the list of most frequent questions that we receive:
| Table of Contents |
|---|
Q: Log4j2 CVE-2021-44228 vulnerability
Capacity Tracker is not impacted by the log4j vulnerability. We do not use our own logging library, we use the one provided by Atlassian.
...
Please only use the remaining estimate.
Q: Story points not reflected in the Capacity Tracker.
This could be possible due the use of a custom field or presence of duplicate fields for Story Point in your Jira instance and Project Settings. Therefore we strongly recommend using default Jira fields for time tracking and estimation that includes Story Points.
Another possibility is due to an inherent edge case in the Jira itself. Earlier classic projects estimation were measured on “Story Points” field in Jira. Later they introduced another default field “Story Point Estimate“ for next-gen and team managed projects that introduced a lot of confusion around Jira user community. This means if you’re using a classic project or company managed project template then you will have to configure and use default “Story Point” field, and if your project is created for next-Gen or team managed configurations then you will have to use default “Story Point Estimate” field. Yes, indeed it is confusing and the same has been recognized by Atlassian in their forums and support tickets.
Your Jira administrator can help you review your current configurations and help fix as necessary.
Q: I'd like to see the capacity at the sub-task level. The Capacity metrics are only reflected at the story level.
...