<!--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=26735) </details> <!--IssueSummary end--> ### Problem to solve allow Jobs API to filter by "manual" or "bridge" jobs only and to retrieve their statuses and other details. ### Target audience - Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney - Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha - Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon - Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney ### Further details Will help to allow building custom integrations or simple notifications to engineers where VM's might need to get auto-restarted, containers purged, etc. if things are not progressing or stuck in a process for a bridge pipeline or manual job for whatever reason. ### Proposal As a DevOps Engineer, I need to ensure that my systems are operational for my Development team and to ensure that bridge jobs are not waiting on stuck resources. I need visibility which jobs, bridge or manual, and their status, to discover those potential stuck resources. ### What does success look like, and how can we measure that? Jobs API can be queried with a new parameter that accepts `"job_type" = [manual, bridge]` ### Links / references