<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=14217) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=14217) </details> <!--IssueSummary end--> ### Release notes ### Problem to solve Currently jobs that are allowed to fail, do not hold such information in the job summary, which can be confusing. This information is visible on the jobs list but not in the job summary (detailed view). #### Job summary (missing tag)  ### Intended users ### User experience goal ### Proposal - Display the same badges in job logs page as the jobs list under the job name(like we present for pipelines on pipeline detail page such as `allowed to fail`, `manual` , that communicate the requirements configured for a job. - These are not to be confused with the `runner-tags` presented in the right side panel. ### Further details ### Permissions and Security ### Documentation ### Availability & Testing ### Available Tier ### Feature Usage Metrics ### What does success look like, and how can we measure that? ### What is the type of buyer? ### Is this a cross-stage feature? ### What is the competitive advantage or differentiation for this feature? ### Links / references