Use project_key to filter Jira issues
What does this MR do and why?
Use project_key to filter Jira issues
When filtering Jira issues by vulnerability_ids use project_key as project filter instead of project_keys
Issue: https://gitlab.com/gitlab-org/security/gitlab/-/issues/1082
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
Screen_Recording_2024-04-24_at_18.50.23 | Screen_Recording_2024-04-24_at_18.46.01 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #1082 (closed) The changes in this merge request enhance the Jira integration for issue tracking in GitLab. Previously, if the Jira integration was enabled but not configured correctly, the integration would fail silently. Now, it will raise an error to alert users of the misconfiguration. Additionally, a new feature allows users to filter Jira issues by vulnerability IDs, providing more flexibility in issue tracking.