⭐️ Ideas for pre-refinement

[Sebastiaan127001]

The following is a list of ideas or frustrations from development teams and Quality-time users that could be eligible for making it a feature request or bug.

Pre-refinement ideas

• consider using the due date of user stories when creating a user story from Quality-time
• consider replacing the use of UUID with something more useful so that URLs are readable again. (problem: some URLs I have created do not work any more)
• entities also need to have sticky headers
• possible bug: entering and issue identifier in the general technical debt input field should do a search for that issue, that does not seem to work now
• like this one and this one, we should consider a way to deduplicate security warnings that are found thought Trivy and OWASP dependency-check for instance matching the same class/file and CVE-id.
• when creating an issue for the uncovered branches metric, it says "fix 27 uncovered branches from SonarQube" instead of "fix 27**%** uncovered branches from SonarQube"
• all the hyperlinks in the footer should have the target="_blank" attribute
• Limit the length of comments when metrics are collapsed. #8281
• when everything on a report is green and grey, Quality-time can give the impression that everything is good while there is still a lot of work to do. Consider implementing a view that shows all outstanding work, like show all metrics that require action; show all metrics that have outstanding work; show all metrics that have a Jira issue linked.
• possibility to temporarily disable the MS Teams notification hook, so that the token is not lost. Sometimes it is not relevant because there is an outage and the MS Teams hook keeps spamming the channel, this is unwanted behaviour but deleting the config in the report is not wanted
• in this article, the term code churn is mentioned. This is an indicator for software quality. Is this possible to create a metric for this? I believe this information is available in the GitLab API.
• for each subject, add a possibility for an additional Jira label
• it must be possible to leave the desired reaction time empty in the configuration
• currently, when installing the metric 'job runs within time period' the link to GitLab or Jenkins does not point to jobs that did run, the link goes to a general page of GitLab or Jenkins, this should be improved
• consider replacing the use of UUID for report and subject identification since this results in unusable URL's

Issues that were left unresolved in the previous pre-refinement list ( #4959 )

• it 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 Jira = "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/.
• Create feature request to accept version numbers with postfix parts. Supply a few examples of version numbers that currently fail.
  see also --> ⭐️ Future Issues for pre-refinement #4959 (comment)

Big Ideas

• remove source up-to-date-ness → while this is valuable information, I believe that this should be part of source management
• auto scan for library version