Here is the list of most frequent questions that we receive:
| Table of Contents |
|---|
Q: Capacity Tracker disappeared from by board
We have deployed a release to enable permissions on team-managed boards and hide UI elements when you don’t have the required permissions.
We have updated our documentation to guide you on how to configure them: Team-managed Projects
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.
You can read Atlassian’s report on their products here: https://confluence.atlassian.com/security/multiple-products-security-advisory-log4j-vulne%5B%E2%80%A6%5D-to-remote-code-execution-cve-2021-44228-1103069934.html
Q: The Original Estimate field does not affect my data after change.
...
Please only use the remaining estimate.
Q: Story points not reflected in the Capacity Tracker.
This could be possible due one of the following reasons:
1) You are using a custom field instead of Jira’s default field. We strongly recommend using default Jira fields for time tracking and estimation that includes Story Points.
2) Wrong story point field. 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. It is a Jira constraint currently and hence a pre-requisite for tracker.
If you are using a “Team-managed project” or “Next-gen projects”, the field should be “Story point estimate”
If you are using a “Company-managed project” or “Classic projects”, the field should be “Story Points”
3) Duplicate story point field or incorrect use of multiple story points fields available in Jira.
Multiple fields called “Story Points” or “Story Points Estimate”. If you are a Jira admin, you can go to https://yourinstance.atlassian.net/secure/admin/ViewCustomFields.jspa?page=1 and look for fields called “Story Points” or “Story point estimate”. If you find multiple fields, then you will have to remove the non standard one. It could be in the list of custom fields, or the Trash screen (if it is pending deletion). You can click on the “Info” icon to get some troubleshooting details, it should show you which field is currently being used by the tracker.
Indeed the multiple and wrong use of fields is confusing and the same has been recognized by Atlassian in their forums and support tickets. Atlassian might be working on a fix long term but until then please make sure you have added the correct field for your project screens, removing the other one to avoid more confusion. 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.
...