Prefix Branch Names with Issue Type

Release notes

As Issue Types continue to mature within GitLab, we have recognized the benefit of letting branches leverage the type as well.

Problem to solve

As GitLab adopts issue types, users are unable to have their branch names inherit the issue type. Our current state (seen below) prevents users from adding different types of protections or approval rules based on the type of incident.

Create MR from Incident: 1-new-incident Create MR from Issue: 1-new-issue

(See more examples of Issue Types that have been proposed)

Intended users

• Delaney (Development Team Lead)

User experience goal

Provide users an easy way to create branch names that follow the type of issue from where they came.

Proposal

Create MR from Incident: incident/1-new-incident Create MR from Issue: issue/1-new-issue

Further details

The branch prefix easily allows users to then add additional protections based on how the issue was categorized by its type.

Permissions and Security

Documentation

Availability & Testing

Available Tier

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