Update UI text and show a disabled button on the protected manual job page when user doesn't have the permissions to run it - Frontend

Release notes

Problem to solve

Currently when a user can't deploy to a protected environment due to insufficient permissions, the manual job page shows the same UI as always, only with the variables form and the "run" button hidden. It causes confusion since we're not communicating why the usual job actions are unavailable.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Rachel (Release Manager)

Metrics

User experience goal

When I'm viewing a deployment job that is protected, I want to know why I don't have access to run that job and who can run it.

Proposal

• Update the UI text on the manual protected job page to explain why the user doesn't have the access to run the job.
• Show a disabled action button.

New UI text:

This job requires a manual action

This deployment job does not run automatically and must be started manually, but you do not have access to this job's protected environment.

The job can only be started by a project member allowed to deploy to the environment.

Permissions and Security

Only the users who aren't allowed to run the protected manual job will see this page.

Documentation

We might have to update the documentation about protected manual jobs and update the screenshot of the manual protected job page if necessary. documentation

• Current docs: https://docs.gitlab.com/ee/ci/jobs/job_control.html#protect-manual-jobs
• MVC might be to just put a small entry in https://docs.gitlab.com/ee/ci/jobs/job_control.html#troubleshooting that lists the exact error message, and points back to the section above.

Availability & Testing

Available Tier

• Free

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Yes, it touches devopsverify and ~"devops::release" (Release PD included for awareness since the change is small).

Links / references

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.