Allow a user to see all their owned scheduled pipelines

Release notes

Problem to solve

When a user (e.g., a GitLab team member) has handed in notice, they want to proactively identify any scheduled pipelines that will break when their account gets blocked after they leave. Currently, there's no way for a user to see all the scheduled pipelines they own across all projects in their GitLab instance.

This creates operational risk when users leave an organization, as scheduled pipelines may fail unexpectedly, and it's difficult to identify which pipelines need ownership transfer beforehand.

Proposal

As a simple starter, we should add a list of owned scheduled pipelines to Profile > Account.

The list should display:

• Links in the format: namespace / project / pipeline_name
• Each link should navigate to the scheduled pipelines page for that project
• Initially, we can start with just active pipelines

Why Profile > Account? There's already a similar list of "Groups you need to transfer ownership for, before you delete your account".

Related Issues

This proposal addresses a gap not covered by existing issues:

• #20762 - "GitLab Admin feature to transfer Scheduled Pipeline Ownership to another user" - This addresses the admin perspective but doesn't help individual users proactively identify their own pipelines
• #404403 (closed) - "View scheduled pipeline config without taking ownership" - This was about viewing pipeline details, not listing owned pipelines (closed/implemented)
• #512601 - "API to assign pipeline schedule ownership to any user" - This is about API functionality for ownership transfer, not user visibility
• #424299 - "Pipeline schedules fail to load if the 'owner' account gets deleted" - This addresses the failure scenario but not prevention
• #520245 - "Allow GitLab administrators to view all details of scheduled pipelines without taking ownership" - This is admin-focused, not user-focused

Intended users

Anyone who creates Scheduled Pipelines. E.g.

• Sasha (Software Developer)
• Priyanka (Platform Engineer)
• Sidney (Systems Administrator)
• Simone (Software Engineer in Test)
• Amy (Application Security Engineer)

Feature Usage Metrics

None.

Does this feature require an audit event?

No.

Implementation Plan

Pipleines by Owner is already well-indexed in the database:

CREATE INDEX index_ci_pipeline_schedules_on_owner_id ON ci_pipeline_schedules USING btree (owner_id);

CREATE INDEX index_ci_pipeline_schedules_on_owner_id_and_id_and_active ON ci_pipeline_schedules USING btree (owner_id, id) WHERE (active = true);