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.

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