Developer-level users no longer able to run pipelines on protected branches

<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=230939) </details> <!--IssueSummary end--> ## Status Update (12th May 2026) The issue that addresses this problem would be resolved by https://gitlab.com/gitlab-org/gitlab/-/work_items/334413 ### Developer-level users no longer able to run pipelines on protected branches Previously we were able to allow developer-level users to run pipelines from protected branches (i.e. master). This has since changed and now only users with master privileges can run these pipelines. This slows our workflow as it restricts developer capabilities too much and also prevents non-critical 'test' deployment options from being run from the master branch. ### Steps to reproduce Create manual pipeline on protected branches (i.e. master), then attempt to run any selection of job as developer. ### Workaround As long as developers have the ability to Merge (which would still require approval before being able to merge), they have the ability to deploy.  :point_up: Succeeds in allowing developers to run pipelines :point_up: Succeeds in allowing developers to run pipelines! Additionally, if it's merely a job that needs to be played / retried (and not a full pipeline), [Protected Environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html#protecting-environments) allow you to add reporters or developers that don't have Run Pipeline access to still play/retry jobs that are tied to a specific environment. ### What is the current _bug_ behavior? Notification on drop-down job selector saying `*job* - manual play action (not allowed)` when attempting to run as developer ### What is the expected _correct_ behavior? Once branch has been merged with master/pipeline has been created on protected branch, all users should be permitted to run jobs. I understand how this could be a useful check for some, but once a branch has been merged with master, that should signify that this version is stable and allowed to be deployed, regardless of whether or not the user is master or not. This option was available previously and has since been changed. This bug happens on gitlab.com

issue