Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Current »


AreaKnown IssueRecommended workaround
1QualityHistory 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.Build a Custom Metric using Custom Metrics v2 (Beta)
2QualityQuality 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.Build a Custom Metric using Custom Metrics v2 (Beta)
3Custom MetricsRenaming 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.
4Project Configuration WizardNo ability to specify settings for GIT and Gerrit metrics.Contact support with appropriate request.
5JIRA data source configurationCombining 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.
6Project Configuration WizardAdvanced configuration - "Estimation variance thresholds" modifications are not applied to any charts / legends at the Estimation screen.Contact support with appropriate request.
7Quality "Bug Growth" by sprints/versionsAssociations 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. Build a Custom Metric using Custom Metrics v2 (Beta)
8Navigation between PERF and HEALTH applicationsIn 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 .


9JIRA data source configurationNot all custom fields can be processed for further usage in a metric calculationBuild a Custom Metric using Custom Metrics v2 (Beta)
10TFS metrics limitationsMetrics based on logged hours history (usually treated as Completed Work in TFS) cannot be calculatedBuild a Custom Metric using Custom Metrics v2 (Beta)
11Metrics calculation by daysMetrics do not take into account specific for a project working hours, they are calculated based on a 24h -dayBuild a Custom Metric using Custom Metrics v2 (Beta)
12AggregationIf a node used for aggregation is moved, then aggregation data will be available only after the next data load is completed.n/a



  • No labels