Skip to content

Scan MR description for Jira issue keys when syncing builds with Jira

Andy Schoenen requested to merge andysoiron/add-jira-connect-mr-description-issue-id-scan-for-builds into master

What does this MR do and why?

This considers the MR description when scanning for Jira issue keys of builds.

Issue keys can be included in:

  • MR titles
  • MR descriptions
  • Branch names
  • Commit messages

Commit messages can not be considered at the moment because the commit needs to be loaded from Gitaly and this can cause N+1 problems when sending multiple builds.

How to set up and validate locally

The setup to test this requires setting up a Jira connect development environment and enabling runners on Gitpod. I'm not listing all of this since this is only a small change but if someone is interested, I can add a video or outline the steps here.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Andy Schoenen

Merge request reports