Improve pipeline subscription UX

Release notes

Problem to solve

The pipeline subscription interface is confusing at best and automatically subscribing back to projects that are subscribed to could create a loop of builds.

!77332 (merged) introduces some changes to bring down the confusion, but the lists could go very long with the proposed pattern.

Intended users

Project maintainers who are likely Sasha (Software Developer)

Metrics

User experience goal

Consider Project A and Project B. Project B has subscribed to Project A and wants to rebuild the project when A is updated.

Possible Use Cases for Maintainer for Project A

• As a maintainer of a public project with downstream subscriptions, I want to see how many projects are subscribed to mine, so I can feel accomplished, tout my project.
• As a maintainer of a public project with downstream subscriptions, I want to remove subscriptions, so I can take my project private.

Possible use cases for maintainer for Project B

• As a maintainer of a project that is subscribed to a public project, I want to remove my subscription, so I can stop building every time it is updated.
• As a maintainer of a project that is subscribed to a public project, I want to see how often the public project is updated, so I can estimate how many build minutes i'll use.

Proposal

Further details

Follow-up from discussion in a bug report about a 404 when trying to remove a project that's subscribed to yours.

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.