Add documentation about how to configure less obvious metrics

[fniessink]

Metrics to document (see https://quality-time.readthedocs.io/en/latest/usage.html#notes-on-specific-metrics for examples of existing documentation):

Bugs

• [ ] Open unresolved bug reports (metric: issues, sources: Jira, Azure DevOps)
• [ ] Open resolved bug reports (metric: issues, sources: Jira, Azure DevOps)
• [ ] Closed bug reports (metric: issues, sources: Jira, Azure DevOps)
• [ ] Total number of bug reports (metric: issues, sources: Jira, Azure DevOps)
• [ ] Open security bug reports (metric: issues, sources: Jira, Azure DevOps)
• [ ] Open security bug reports from pentestreport (metric: issues, sources: manual number, generic JSON)

Logical test cases

• [ ] Number of automated logical test cases (metric: issues, sources: Jira)
• [ ] Number of manual logical test cases (metric: issues, sources: Jira)
• [ ] Number of obsolete logical test cases (called "will not execute" at ICTU, metric: issues, sources: Jira)
• [ ] Total number of logical test cases (metric: issues, sources: Jira)
• [ ] Duration of manual logical test cases
• [ ] Number of manual logical test cases that have not been executed recently
• [ ] Number of manual logical test cases with unknown duration
• [ ] User stories or use cases without logical test cases
• [ ] Logical test cases that have not been reviewed
• [ ] Test status of logical test cases (metric: test cases, sources: Jira and one or more test reports)

Scrum

• [ ] Number of ready user stories
• [ ] Number of points of ready user stories
• [ ] Number of user stories in progress
• [ ] Velocity
• [ ] Number of technical debt issues
• [ ] Number of ready user stories that have not been assessed for security/performance/architectural risks
• [ ] Number of ready user stories with high and/or medium security/performance/architectural risks

Periodic activities

• [ ] Time since last self-assessment
• [ ] Time since last security test

Meta

• [ ] Number of missing metrics
• [ ] Number of red metrics

---

Related Kwaliteitsaanpak ticket: https://github.com/ICTU/Kwaliteitsaanpak/issues/413

[Sebastiaan127001]

The “issues metric” is a versatile metric that can be used for a variety of purposes. This metric can use four different sources i.e. Jira, Azure DevOps Server, Trello or Manual number. When using it in conjunction with Jira this metric displays the result of a Jira query. This is done using the JQL syntax. More information on this can be found on the Jira page. (https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/) In general, one can compose the query by navigating to Jira —> Issues —> Search for Issues. On this page the option “advanced search” can be activated and the JQL query can be composed and the results of it can be viewed instantly. An example of a basic query is “assignee = currentUser() order by updated DESC”. To create advanced queries take a look at https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/

[Sebastiaan127001]

@fniessink is this what you had in mind?