Add Label Events to the GraphQL API

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Release notes

We want the GraphQL API to be the primary means of interacting programmatically with GitLab. To achieve this, it needs full coverage - anything possible in the REST API should also be possible in the GraphQL API. Today we are proud to announce the availability of Resources Label Events in our GraphQL API.

Problem to solve

We're a big consumer, among many others, of labels. In Epics, Issues, Merge Requests, our workflows are mostly (if not entirely) driven by labels. To automate these workflows, and for compliance reasons, we need to be able to get information on the labels activity. The resource is already available in the Rest API, but not in the GraphQL one yet.

Intended users

Unknown.

User experience goal

The user should be able to use the API with GitLab to fetch issues, merge requests, or epics with their Labels Events, to avoid mixing GraphQL queries and Rest.

Proposal

Implement the resource in GraphQL.

Further details

The type would be an IssuableLabelEvents array with the fields:

Field Type Description
id ID! Internal ID
user UserConnection Author of the event
created_at Time
label LabelConnection Label of the resource
action LabelEventsEnum! "add" or "remove"

Permissions and Security

No change

Documentation

Update https://docs.gitlab.com/ee/api/graphql/reference/index.html

Availability & Testing

Available Tier

Free

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by 🤖 GitLab Bot 🤖