Feature adoption is based on usage in the previous calendar month. Data is updated on the first day
DevOps Adoption shows feature adoption data for groups and subgroups for the previous calendar month.
of each month. If the monthly update fails, it tries again daily until successful.
## Enable data processing
A feature shows as **adopted** when a group has used the feature in a project during the time period.
This includes projects in any subgroups of the group. For example, if an issue was created in a project in a group, the group has adopted issues in that time.
Group DevOps Adoption relies on data that has been gathered by a weekly data processing task.
### Exceptions to feature adoption data
This task is disabled by default.
To begin using Group DevOps Adoption, access the feature for the first time. GitLab automatically
When GitLab measures DevOps Adoption, some common DevOps information is not included:
enables the data processing for that group. The group data doesn't appear immediately, because
GitLab requires around a minute to process it.
## What is displayed
- Dormant projects. It doesn't matter how many projects in the group use a feature. Even if you have many dormant projects, it doesn't lower the adoption.
- New GitLab features. Adoption is the total number of features adopted, not the percent of features.
DevOps Adoption displays feature adoption data for the given group
## When DevOps Adoption data is gathered
and any added subgroups for the current calendar month.
Each group appears as a separate row in the table.
For each row, a feature is considered "adopted" if it has been used in a project in the given group
during the time period (including projects in any subgroups of the given group).
## Adoption over time
A weekly task processes data for DevOps Adoption. This task is disabled until you access
DevOps Adoption for a group for the first time.
The **Adoption over time** chart in the **Overview** tab displays DevOps Adoption over time. The chart displays the total number of adopted features from the previous twelve months,
The data processing task updates the data on the first day of each month. If the monthly update
from when you enabled DevOps Adoption for the group.
fails, the task tries daily until it succeeds.
The tooltip displays information about the features tracked for individual months.
DevOps Adoption data may take up to a minute to appear while GitLab processes the group's data.
## When is a feature considered adopted
## View feature adoption over time
A feature is considered "adopted" if it has been used anywhere in the group in the specified time.
The **Adoption over time** chart shows the total number of adopted features from the previous
For example, if an issue was created in one project in a group, the group is considered to have
twelve months. The chart only shows data from when you enabled DevOps Adoption for the group.
"adopted" issues in that time.
## No penalties for common adoption patterns
To view feature adoption over time:
DevOps Adoption is designed not to penalize for any circumstances or practices that are common in DevOps.
1. On the top bar, select **Menu > Groups** and find your group.
Following this guideline, GitLab doesn't penalize for:
1. On the left sidebar, select **Analytics > DevOps adoption**.
1. Select the **Overview** tab.
1. Having dormant projects. It's common for groups to have a mix of active and dormant projects,
Tooltips display information about the features tracked for individual months.
so we should not consider adoption to be low if there are relatively many dormant projects.
This means we should not measure adoption by how many projects in the group have used a feature,
only by whether a feature was used anywhere in the group.
1. GitLab adding new features over time. It's common for group feature usage to be consistent
over time, so we should not consider adoption to have decreased if GitLab adds features.
This means we should not measure adoption by percentages, only total counts.
## Add a subgroup
## Add or remove a subgroup
DevOps Adoption can also display data for subgroups within the given group,
To add or remove a subgroup from the DevOps Adoption report:
to show you differences in adoption across the group.
To add subgroups to your Group DevOps Adoption report:
1. Select **Add or remove subgroups**.
1. Select **Add or remove subgroups**.
1. Select the subgroups you want to add and select **Save changes**.
1. Select the subgroup you want to add or remove and select **Save changes**.
The subgroup data might not appear immediately, because GitLab requires around a minute to collect
It may take up to a minute for subgroup data to appear while GitLab collects the data.
