Open fniessink opened 3 years ago
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/
@fniessink is this what you had in mind?
Metrics to document (see https://quality-time.readthedocs.io/en/latest/usage.html#notes-on-specific-metrics for examples of existing documentation):
Bugs
Logical test cases
Scrum
Periodic activities
Meta
Related Kwaliteitsaanpak ticket: https://github.com/ICTU/Kwaliteitsaanpak/issues/413