Adds new issue_id and mr_id fields fields to workflows api
What does this MR do and why?
This MR partially addresses #570291 by implementing the backend GraphQL changes required to support displaying agent names in Duo workflow system notes.
It adds the newly issue_id and merge_request_id fields (see migration MR implementation) to the backend.
This is part 1 of a 2-part implementation, split from this MR to follow best practices for GraphQL field additions.
Why split the MR?
Adding new GraphQL fields and immediately consuming them in the frontend can cause issues during rolling deployments:
The Problem
- During deployments, frontend code may deploy before backend changes are fully rolled out
- Frontend requests new GraphQL fields => backend doesn't recognize them yet which leads to GraphQL errors
- This can make parts of the application unresponsive until the backend catches up
The Solution and Next Steps
This MR add new GraphQL fields to the backend and is a blocker for the follow up MR which will consume the new fields in the frontend (example).
This approach ensures the backend fields are available before any frontend code attempts to use them, preventing errors on both GitLab.com (during rolling deployments) and self-managed instances (during upgrades).
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.