v5.48.2

v5.48.2 - 2026-01-09

Fixed

• When measuring source up-to-dateness or source version with OWASP Dependency Check JSON reports located in GitLab, parsing the JSON would fail because GitLab returns the JSON files with mimetype application/octet-stream. Fixes #12323.

v5.48.2-rc.0

v5.48.1 - 2025-12-19

Fixed

• When measuring security warnings using SonarQube as source, security violations can be filtered by directory but security hotspots can not, as SonarQube does not support filtering hotspots by directory. Note this in the parameter help. Fixes #12340.
• When using SonarQube as source, don't show the "directories to include" parameter for metrics where SonarQube does not support filtering by directory. Fixes #12341.
• The notifier would fail to notify about metrics without a unit, such as the version metric. Fixes #12412.

v5.48.1

v5.48.1 - 2025-12-19

Fixed

• When measuring security warnings using SonarQube as source, security violations can be filtered by directory but security hotspots can not, as SonarQube does not support filtering hotspots by directory. Note this in the parameter help. Fixes #12340.
• When using SonarQube as source, don't show the "directories to include" parameter for metrics where SonarQube does not support filtering by directory. Fixes #12341.
• The notifier would fail to notify about metrics without a unit, such as the version metric. Fixes #12412.

v5.48.1-rc.0

v5.48.0 - 2025-12-12

Fixed

• When measuring issues with Jira as source, the names of sprints that issues belong to would not be correct. Fixes #12328.

Changed

• Rename the 'tests' metric to 'test results' and the 'test suites' metric to 'test suite results' to better distinguish them from the 'test cases' metric. 'Tests' and 'test suites' metrics whose default name has not been overriden will automatically use the new default name. Closes #12322.

Added

• When using a calendar data as source, allow for configuring a recurrence pattern and clicking a button to quickly set the next date. Closes #11897.
• When adding metrics to subjects, allow for hiding metric types already used in the subject or in the whole report. Closes #12374.
• When measuring missing metrics, allow for ignoring specific metric types. Closes #12377.
• When measuring missing metrics, allow for ignoring metric types that have been used at least once. Closes #12384.

v5.48.0

v5.48.0 - 2025-12-12

Fixed

• When measuring issues with Jira as source, the names of sprints that issues belong to would not be correct. Fixes #12328.

Changed

• Rename the 'tests' metric to 'test results' and the 'test suites' metric to 'test suite results' to better distinguish them from the 'test cases' metric. 'Tests' and 'test suites' metrics whose default name has not been overriden will automatically use the new default name. Closes #12322.

Added

• When using a calendar data as source, allow for configuring a recurrence pattern and clicking a button to quickly set the next date. Closes #11897.
• When adding metrics to subjects, allow for hiding metric types already used in the subject or in the whole report. Closes #12374.
• When measuring missing metrics, allow for ignoring specific metric types. Closes #12377.
• When measuring missing metrics, allow for ignoring metric types that have been used at least once. Closes #12384.

v5.48.0-rc.2

v5.47.2 - 2025-12-05

Fixed

• Jira Cloud could not be used as issue tracker because the Jira API version could not be set to v3 when configuring Jira as issue tracker. Fixes #12107.
• When the direction of a metric that by default takes the minimum of multiple sources is reversed, take the maximum. And vice versa. Fixes #12142.
• Composite subjects with a default name would be shown as having the name 'None' in the changelog. Fixes #12318.

v5.47.2

v5.47.2 - 2025-12-05

Fixed

• When the direction of a metric that by default takes the minimum of multiple sources is reversed, take the maximum. And vice versa. Fixes #12142.
• Composite subjects with a default name would be shown as having the name 'None' in the changelog. Fixes #12318.

v5.47.2-rc.0

v5.47.1 - 2025-11-28

Fixed

• The label and help text of the technical debt target field were colored red as if the field is mandatory. Fixes #12300.

Removed

• Removed database migration code. As always, if your currently installed Quality-time version is not the penultimate version, check the upgrade path in the versioning policy before upgrading. Closes #12289.

v5.47.1

v5.47.1 - 2025-11-28

Fixed

• The label and help text of the technical debt target field were colored red as if the field is mandatory. Fixes #12300.

Removed

• Removed database migration code. As always, if your currently installed Quality-time version is not the penultimate version, check the upgrade path in the versioning policy before upgrading. Closes #12289.

v5.47.1-rc.0

v5.47.0 - 2025-11-20

Fixed

• Clarify in the product vision that checking the correct configuration of sources is out of scope for Quality-time. Fixes #3821.
• When using Cobertura XML files as source, be prepared for timestamps without milliseconds. Also, report an error if the timestamp is missing. Fixes #12247.
• Don't allow floats with the manual number source. Fixes #12261.
• When measuring suppressed violations with SonarQube as source, take the impacted software qualities into account if configured by the user. Fixes #12263.
• Source configurations in the report source overview did not display parameter values. Fixes #12281.

Added

• When measuring commented out code, complex units, long units, many parameters, security warnings, suppressed violations, todo and fixme comments or violations with SonarQube as source, allow for specifying directories to include. Closes #12189.