2019-09-04 21:01:54 +05:30
---
2022-11-25 23:54:43 +05:30
stage: Plan
2021-02-22 17:27:13 +05:30
group: Optimize
2022-11-25 23:54:43 +05:30
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
2019-09-04 21:01:54 +05:30
---
2022-10-11 01:57:18 +05:30
# Insights for groups **(ULTIMATE)**
2019-07-31 22:56:46 +05:30
2021-12-11 22:18:48 +05:30
> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/725) in GitLab 12.0.
2019-07-31 22:56:46 +05:30
2022-11-25 23:54:43 +05:30
Configure insights to explore data about you group's activity, such as
2022-10-11 01:57:18 +05:30
triage hygiene, issues created or closed in a given period, and average time for merge
requests to be merged.
2022-11-25 23:54:43 +05:30
You can also create custom insights reports that are relevant for your group.
2019-07-31 22:56:46 +05:30
2022-11-25 23:54:43 +05:30
## View group insights
2019-09-04 21:01:54 +05:30
2022-10-11 01:57:18 +05:30
Prerequisites:
- You must have [permission ](../../permissions.md#group-members-permissions ) to view the group.
- You must have access to a project to view information about its merge requests and issues,
and permission to view them if they are confidential.
2022-11-25 23:54:43 +05:30
To access your group's insights:
2019-09-04 21:01:54 +05:30
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Groups** and find your group.
2021-11-18 22:05:49 +05:30
1. On the left sidebar, select **Analytics > Insights** .
2019-07-31 22:56:46 +05:30
2022-11-25 23:54:43 +05:30
## Interact with insights charts
2022-10-11 01:57:18 +05:30
2022-11-25 23:54:43 +05:30
You can interact with the insights charts to view details about your group's activity.
2019-07-31 22:56:46 +05:30
2022-11-25 23:54:43 +05:30
### Display different reports
To display one of the available reports on the insights page, from the **Select report** dropdown list,
select the report you want to display.
### View bar chart annotations
To view annotations, hover over each bar in the chart.
### Zoom in on chart
Insights display data from the last 90 days. You can zoom in to display data only from a subset of the 90-day range.
To do this, select the pause icons (**{status-paused}**) and slide them along the horizontal axis:
- To select a later start date, slide the left pause icon to the right.
- To select an earlier end date, slide the right pause icon to the left.
### Exclude dimensions from charts
By default, insights display all available dimensions on the chart.
To exclude a dimension, from the legend below the chart, select the name of the dimension.
## Configure group insights
GitLab reads insights from the
2022-10-11 01:57:18 +05:30
[default configuration file ](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/fixtures/insights/default.yml ).
2019-07-31 22:56:46 +05:30
2022-11-25 23:54:43 +05:30
To configure group insights:
2022-10-11 01:57:18 +05:30
2022-11-25 23:54:43 +05:30
1. Create a new file [`.gitlab/insights.yml` ](../../project/insights/index.md#configure-project-insights )
2021-11-18 22:05:49 +05:30
in a project that belongs to your group.
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Groups** and find your group.
2021-11-18 22:05:49 +05:30
1. On the left sidebar, select **Settings > General** .
2023-07-09 08:55:56 +05:30
1. Expand the **Analytics** tab and find the **Insights** section.
2021-11-18 22:05:49 +05:30
1. Select the project that contains your `.gitlab/insights.yml` configuration file.
1. Select **Save changes** .
2019-07-31 22:56:46 +05:30
2019-09-04 21:01:54 +05:30
<!-- ## 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.
2023-01-13 00:05:48 +05:30
Each scenario can be a third-level heading, for example `### Getting error message X` .
2019-09-04 21:01:54 +05:30
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. -->
