60 lines
2.3 KiB
Markdown
60 lines
2.3 KiB
Markdown
---
|
|
type: reference
|
|
stage: Plan
|
|
group: Project Management
|
|
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
|
---
|
|
|
|
# Issue analytics for groups **(PREMIUM)**
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7478) in GitLab 11.5.
|
|
|
|
Issue analytics is a bar graph which illustrates the number of issues created each month.
|
|
The default time span is 13 months, which includes the current month, and the 12 months
|
|
prior.
|
|
|
|
To access the chart:
|
|
|
|
1. On the top bar, select **Main menu > Groups** and find your group.
|
|
1. On the left sidebar, select **Analytics > Issue Analytics**.
|
|
|
|
Hover over each bar to see the total number of issues.
|
|
|
|
To narrow the scope of issues included in the graph, enter your criteria in the
|
|
**Search or filter results...** field. Criteria from the following list can be typed in or selected from a menu:
|
|
|
|
- Author
|
|
- Assignee
|
|
- Milestone
|
|
- Label
|
|
- My reaction
|
|
- Weight
|
|
|
|
You can change the total number of months displayed by setting a URL parameter.
|
|
For example, `https://gitlab.com/groups/gitlab-org/-/issues_analytics?months_back=15`
|
|
shows a total of 15 months for the chart in the GitLab.org group.
|
|
|
|
|
|
|
|
## Drill into the information
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/196547) in GitLab 13.1.
|
|
|
|
You can examine details of individual issues by browsing the table
|
|
located below the chart.
|
|
|
|
The chart displays the top 100 issues based on the global page filters.
|
|
|
|
|
|
|
|
<!-- ## Troubleshooting
|
|
|
|
Include any troubleshooting steps that you can foresee. If you know beforehand what issues
|
|
one might have when setting this up, or when something is changed, or on upgrading, it's
|
|
important to describe those, too. Think of things that may go wrong and include them here.
|
|
This is important to minimize requests for support, and to avoid doc comments with
|
|
questions that you know someone might ask.
|
|
|
|
Each scenario can be a third-level heading, e.g. `### Getting error message X`.
|
|
If you have none to add when creating a doc, leave this section in place
|
|
but commented out to help encourage others to add to it in the future. -->
|