You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
project G requested me to show the number of realised issues in the last sprint (this is not possible though JQL, but the info is available). Another use case for this came from project F:
As a quality manager, I would like to see the percentage of issues with label X that have been part of the previously closed sprint. (what percentage were tech debt stories?). This should become possible when Allow for calculation when adding multiple sources #5098 is implemented.
Several of my project face the problem of running out of nexus storage during software development. Can we add a collector to fetch the percentage of used storage on a Nexus host? No, is monitoring; outside scope Quality-time. There is an issue in progress to add this to the development platform at ICTU (IES-5817).
in relation to make Quality-time a more mature report (Monitor the quality of the quality management #4069) I would be useful to have the option for the user to use variables in the comment field. For this we need a section to store the placeholders and the related text. Like = "https://jira.organisation.com/". Unfortunately, Quality-time uses HTML for comments at the moment which doesn't support variables. One alternative may be to switch to Markdown for comments and investigate whether Markdown variables may offer a solution. See https://www.brianchildress.co/variables-in-markdown/.
build collector for mocha so that Quality-time can read mochaweome.json which shows Cypress test results. @Sebastiaan127001 checks whether the JUnit report of Cypress can be used instead.
In relation to this issue: Distinguish between direct and indirect metrics. #4931 SonarQube can be a compound metric too. Violations versus the separate violations like 'long units'. The metrics for specific violation types ('long units', 'too many parameter', etc.) already support the percentage scale. The violations metric does not. Note that the percentage scale for the violations metric only makes sense when filtering violations by type or severity otherwise the percentage is always 100%.
@fniessink as promised, I hereby include a list of software versions that development teams use, but that do not match the semver / pep standard and therefore break the software version metric.
team F
230216.post60271390
230215-a217ad48
230208-4806c8d0
@fniessink as promised. I have discussed with the team the benefits of Mocha Awesome test reporter compared to JUnit. The team (G) stated that both reports contain the same information that Quality-time needs. The team advises, however, to, eventually, create a collector for the Mocha Awesome JSON since this is the standard for Cypress. The JUnit format was initially intended for unit test reports.
Project requests
As a quality manager, I would like to see the percentage of issues with label X that have been part of the previously closed sprint. (what percentage were tech debt stories?). This should become possible when Allow for calculation when adding multiple sources #5098 is implemented.
New improvement ideas
The text was updated successfully, but these errors were encountered: