Frontend: Store the pipeline editor popovers state in the database

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

• Close this issue

Release notes

Problem to solve

In the pipeline editor we have two permanently dismissible popovers that store their state in the local storage, which means they're not truly permanently dismissible.

• The file tree popover
• The onboarding popover

Storing the popovers state in the database would ensure they only show up to a user once.

For more context see this issue thread.

Proposal

Store the popovers dismissed state in the database.

Intended users

Feature Usage Metrics

Implementation

The breakdown for this feature is as follows:

Work Type	Description	Issue Link
backend	Expose includes link (initial MVC)	#344937 (closed)
frontend	Change the pipeline editor fixed layout to full-width	#346331 (closed)
frontend	Introduce the feature flag and the empty drawer.	#350721 (closed)
frontend	Pass down the content to the drawer and format it properly	#350722 (closed)
frontend	Remember the open/closed state in local storage	#350723 (closed)
frontend	Add feature discovery popover	#360111 (closed)
frontend	Roll out feature flag	#350724 (closed)
backend	Backend: Add toggle flag to UserCalloutFeatureNameEnum to allow for popover dismissal	#365347
frontend	Store the pipeline editor popovers state in the database	👈 You are here
backend	Add messaging when files can't be fetched due to invalid CI configuration	#360431

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.