Src API returns a 500 exception when issue keys are enforced

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      Making a commit on a repo that has `Require issue keys in commit messages` enabled returns a 500 error. Since this can be fixed by the user, it should return a 4xx error.

      Steps to Reproduce

      1. Link a Bitbucket repository to an issue tracker
      1. Under Repository Settings > Workflows > Links, enable the option Require issue keys in commit messages
      1. Make a commit using the src API without an issue key in the commit message.
      2. See 500 status code

      Expected Results

      4xx status code since it can be fixed by the user. 

      Actual Results

      500 status code

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            James Kim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: