Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-3741

Make GIT Commit require a Jira-Issue-ID (configurable)

    XMLWordPrintable

Details

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      In our company we have several projects that are used in their subversion integration to have hook scripts that check the commit-comment to contain a jira-issue-id, some people "extended" them to make a specific jira-issue-id prefix as requirement.
      As git uses on "server" side only push/pull methods maybe stash should be able to check the commit comments that differ from it's repository version to have jira-id's referenced and if not deny the push...
      Anyway this case must be thought of precisely but my feature request may be clear now:

      Please provide a way to require the git repositories hosted by STASH to contain a Jira-ID in it's commit comments. This feature shall be configurable per Repository (or Branch...)

      We maybe can discuss the details here hopefully we can find a common sense to implement this feature request.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              herzog@t-systems.com_match herzog@t-systems.com_match
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: