Better Commit Policy for Jira Server/Data Center: Feature Requests
Ideas and requests for new features. Suggest ideas. Vote for the best. See what's planned.
- Verify the "from branch" when starting a new branch
- Add affected issue metadata to REST API verification endpoint response
- Support GitKraken
- Modify the commit message automatically
- Verify pull request meta information (name, description, date, source branch, target branch, etc.) verifiable
- Optionally hide username from JQL-related rejection messages
- Support for Bitbucket Cloud server-side verification (in the Jira Server / Data Center app version)
- Support for GitHub.com server-side verification
- Better Commit Policy for Jira Cloud
- Custom conditions written in Groovy or as executable commandlines
- Better Commit Policy for Jira Cloud + Bitbucket Cloud
- Support for Perforce
- Give "heuristic hints" about probable and potential issue keys when the "Commit message must contain issue keys from a JQL query" condition rejects the commit
- Policy replication / template based policies
- "Share policy" feature to easily ask developers to install the hook for a policy to their local clone repositories
- Support verification of code changes (diffs)
- Add "user in Jira" tag condition type
- Add key-value pairs to Bitbucket hook configuration UI and pass them as commit policy variables to the Jira component
- New tag/branch condition: "tag/branch name contains a valid version in Jira" (unreleased or any)
- Only verify "at least one" commit in a bunch of commits
- Support for GitLab CE/EE (via a custom GitLab extension)
- Make it possible for a rule to only verify merge commits and nothing else
- Support for GitHub Enterprise
- Provide a "soft mode", where policies warn users, but do not reject the commit
- Tracking the last verification per policy and per repository
- REST API should allow creating / updating / deleting policies
- Customizable permissions for policy management
- Post-mortem mechanism to capture those pushes that violate a policy even if you can't manage the hooks in the target repository (better late than never)
- Automatically or semi-automatically notify developers when the policy goes live, updated or deleted
- Support for GitLab.com (Saas edition) server-side verification