Description | Fix Version | Additional Information |
|---|---|---|
Updating a profile gives the wrong status code. | 3.33.3 | |
JIRA integration - for the basic auth integration, when mandatory keys are missing in the payload,the response should mention which exact keys are missing. | 3.33.3 | |
JIRA integration - for the oauth1 auth integration, when mandatory keys are missing in the payload,the response should mention which exact keys are missing. | 3.33.3 | |
JIRA integration - for the oauth2 auth integration, when mandatory keys are missing in the payload,the response should mention which exact keys are missing. | 3.33.3 | |
Some oauth2 fields are missing when clicking edit for the first time after creation. | ||
JIRA integration - the API allows the creation of an integration with empty values. | 3.33.3 | |
JIRA integration - the validation of the auth type during creation and update is missing, which means that the user can create an integration with any authType. | 3.33.3 | |
JIRA integration - the status code when trying to delete a non-existent integration is shown as 200 instead of 404. | 3.33.3 | |
JIRA integration - the status code when using an invalid integration name is 200 instead of 404. | 3.33.3 | |
JIRA integration - the status code when trying to get the issue types with an invalid integration name and ticketing project is 500 instead of 404 (when specifying which parameter is wrong). | 3.33.3 | |
JIRA integration - the status code when trying to get all Jira projects with an invalid integration name is 500 instead of 404. | 3.33.3 | |
JIRA integration - the status code when trying to get all labels with an invalid integration name is 500 instead of 404. | ||
While generating a public key, clicking the eye icon and then clicking copy creates different spacing in the public key compared to the key spacing without clicking the icon. |