Add ability to lock Epics

Release notes

For large projects with many contributors, it may be useful to stop threads in epics, isses or merge requests in these scenarios:

• The project maintainer has already resolved the thread and it is not helpful for continued feedback.
• The project maintainer has already directed new conversation to newer issues or merge requests.
• The people participating in the thread are trolling, abusive, or otherwise being unproductive.

Problem to solve

We can currently lock Issues and Merge Requests when no more comments should be added, but we cannot lock Epics.

When an Epic is attracting unwanted comments, the current options include only making the Epic confidential.

Intended users

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/

• Cameron (Compliance Manager)
• Parker (Product Manager)
• Delaney (Development Team Lead)
• Sam (Security Analyst)
• Rachel (Release Manager)
• Allison (Application Ops)
• Eddie (Content Editor)

User experience goal

Privileged users should be able to lock Epics.

Proposal

Add a "Lock Epic" button similar to that on issues.

Further details

See discussion on https://gitlab.com/groups/gitlab-org/-/epics/3600

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

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.