Mark items as "Ready for (re)deployment" and notify the deployment owner

In teams using Deployment Pipelines, developers build items but a separate person (often an architect or release manager) promotes them through Dev → Test → Acceptance → Production. Fabric has no native, built-in way for developers to signal which items are ready. Handoff happens over Teams, email, or spreadsheets, which leads to missed items, partial deployments of interdependent items, and confusion about what's ready versus still in progress.

Proposed solution

• A "Mark as ready for deployment" action on any workspace item, with an optional note.
• The option to group items into a named "release set," so dependent items (e.g. a notebook, pipeline, and dataflows) are deployed together.
• A notification to the designated deployment owner of the pipeline stage.
• A "Ready" filter and status column in the Deployment Pipelines compare view, so the deployer can select exactly the flagged items.
• Status tracking (Ready, Deployed, Rejected with a comment) and an audit history.

Benefits

• Clear ownership and a clean handoff between developers and deployers.
• Fewer broken deployments caused by missing dependencies.
• Traceability of what was released, when, and at whose request, which is useful for governance and audits.