The Jira Key in Branchname Merge Check Plugin is a Bitbucket add-on that enforces the presence of a Jira key in branch names during the merge process. This plugin helps maintain consistency and traceability between Jira issues and Bitbucket branches.
- Automatically validates branch names for the presence of a Jira key.
- Prevents merges if the Jira key is missing from the branch name.
- Enhances integration and traceability between Jira and Bitbucket.
- Download the Branchname Jira Key Merge-check for Bitbucket from the Bitbucket Marketplace.
- Install the plugin in your Bitbucket instance.
- Configure the merge-check settings in repository or project settings panel.
- Create a new branch or update an existing branch in your Bitbucket repository.
- Ensure that the branch name includes a valid Jira key in the format
PROJ-123. - Open a pull request to merge the branch into the target branch.
- The merge check will verify the presence of the Jira key in the branch name.
- If the Jira key is missing, the merge process will be blocked with an error message.
Branchname Jira Key Merge-check for Bitbucket can be configured in the Bitbucket administration panel. Follow these steps to configure the plugin:
- Go to the repository or project administration panel.
- Navigate to the merge-checks and enable/edit "Jira ticket reference in branch name".
- Customize the plugin behavior.
- Save the configuration changes.
This plugin is licensed under the Apache 2.0 License. See the LICENSE file for more details.
We welcome contributions to enhance the Branchname Jira Key Merge-check for Bitbucket. To contribute, please follow these guidelines:
- Fork the repository and create a new branch.
- Make your code changes or enhancements.
- Submit a pull request with a clear description of the changes.
See the CHANGELOG.md file for the version history and changes made in each release.
Branchname Jira Key Merge-check for Bitbucket is developed and maintained by @asmild.
See the PRIVACY file