Bitbucket Cloud REST API 400 or 422 response when a field is not supported or available

XMLWordPrintable

    • 1

      Currently, some REST API endpoint is responding with 500 error message when a field is not supported or unavailable.

      Feature request:
      Respond with 400 or 422 instead of 500 to make it clear that the field is not supported or does not exist.

            Assignee:
            Unassigned
            Reporter:
            Mark C
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: