Replace Job links with job component in issues and merge requests

Problem to solve / Proposal

Much like we replace any Merge Request or Issue with a short link; https://gitlab.com/my/project/merge_requests/123 => !123, https://gitlab.com/my/project/issues/123 => #123

A nice UX improvement would be to include a partial rendering for the job as we do with the Pipelines page.

Before

After

Intended users

• Parker (Product Manager)
• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Presley (Product Designer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)
• Sam (Security Analyst)
• Dana (Data Analyst)

Permissions and Security

If the user does not have access to the job link - render the link as-is without the component.

Testing

Tests would need to be written to check for the permission issues as described in the above section.

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

• In an issue or merge request, when a user links a specific job ID (/:project/-/jobs/:job_id); Render the job component as we do in the pipelines page
  • 
• When a job is linked, the current status of that job would be rendered in the component. (Created, Pending, Running, Success, Failed)
• If the logged in user does not have access to view the job page, render the link as text.
• The component should not have the retry button as it does in the picture
• The entirety of the component should be a link to the job

What is the type of buyer?

Core / Free +

Links / references