Add boundary to Jira issue key regex to stricken issue detection
What does this MR do and why?
This merge request aims to solve the issue: #327327 (closed) by adding boundary to the jira_issue_key_regex so it does not find tickets in the format TICKET-[0-9]+-[0-9]+.
How to set up and validate locally
- Enable Jira integration
- Commit a change with TICKET-12345-455 in the commit msg
- Observe the result in GitLab: TICKET-12345-455
An example project: https://gitlab.com/twouters/jira-tickets
Relevant commit example twouters/jira-tickets@dfa10f10
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Furkan Taşdemir