Overview

Jira is the source of truth for any work being done, however if engineers are opening pull requests without a Jira issue, this means there are hidden work being done. Hidden work are nightmare for product managers on estimation and capacity planning.

In this blog we'll go over common CI tools on how we can enforce all pull requests having linked to a Jira issue.

Create a new workflow by creating .yml file under .github/workflows directory. After a pull request is push/updated GitHub will automatically run the action to validate if pull request is linked to any Jira Issue.

Recommended: jira-pr-link-action

Create a new pipeline by creating .gitlab-ci.yml file at the root of your repository. Pipeline will run every time you make changes to the source branch for a merge request and will validate if merge request is linked to valid Jira Issue.

Recommended: Gitlab CI Code

Bitbucket has its own setting to require issue keys in commit messages which is also helpful to enforce Jira issue pull request matching. To enable this feature you need to visit Repository Settings/Links page.

Recommended: Create a repository link

For Jenkins there are multiple plugins exist in the market place. We selected couple of them for you to validate if pull request is linked to any Jira issue.

Recommended:

Note: For any further questions contact [email protected].
​
​