| Area | Known Issue | Recommended workaround | |
|---|---|---|---|
| 1 | Quality | History of issue types is not taken into account while computing quality metrics. For example, if a month ago a Bug was converted into Improvement, algorithms will consider this item as Improvement (not Bug) regardless of a point on a timeline for which a particular metric is currently calculated. | n/a |
| 2 | Quality | Quality Debt chart: if no defects of a specific priority fixed in the past, it's not possible to compute an approximate debt for open defects of same priority. | n/a |
| 3 | Custom Metrics | Renaming of metric fields is not supported. | If you need to modify a structure of a metric you've defined earlier - you may only add new fields. |
| 4 | Project Configuration Wizard | No ability to specify settings for GIT and Gerrit metrics. | Contact AskPerf@epam.com with appropriate request. |
| 5 | JIRA data source configuration | Combining issues from multiple projects under one Saved Filter can work inadequately: because only one Project Key is taken as a baseline for the configuration - list of issue types, list of workflows, etc. | Combine under saved filters only those projects in JIRA which have identical or similar Issue Types, Workflows and other project settings. |
| 6 | Project Configuration Wizard | Advanced configuration - "Estimation variance thresholds" modifications are not applied to any charts / legends at the Estimation screen. | n/a, use default ones. |
| 7 | JIRA daily data import | Incremental update doesn't detect deleted issues, issues with modified/renamed Versions. | Launch a "full" JIRA data import or wait until a full data load runs automatically over the nearest weekend. |
| 8 | Quality "Bug Growth" by sprints/versions | Associations of bugs per Sprints and Releases is tracked via matching into calendar dates of appropriate sprint or release, NOT by assignment/linkage to a sprint or release. For example, if a bug was fixed over weekend between two adjacent sprints - it will not appear in Bugs Growth statistics. | n/a |
| 9 | Navigation between PERF and HEALTH applications | In case a project/stream in HEALTH does not have configured project/node, PERF will not display metrics for such projects. | Create a consistent set of Streams in HEALTH app mapped to appropriate sub-nodes in PERF. Configure a project in PERF by UPSA ID for being able to get appropriate metrics for the required project in HEALTH . |
| 10 | JIRA data source configuration | Not all custom fields can be processed for further usage in a metric calculation | n/a |
| 11 | TFS metrics limitations | Metrics based on logged hours history (usually treated as Completed Work in TFS) cannot be calculated | n/a |
| 12 | Metrics calculation by days | Metrics do not take into account specific for a project working hours, they are calculated based on a 24h -day | n/a |
| 13 | Aggregation | If a node used for aggregation is moved, then aggregation data will be available only after the next data load is completed. | n/a |
Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.