-
Bug
-
Resolution: Not a bug
-
High
-
5
-
Severity 2 - Major
-
2
-
Issue Summary
When using the Create Issue V3 Rest API, if you provide a description greater than 32767 characters, the API call will fail with the following error:
{ "errorMessages": [ "CONTENT_LIMIT_EXCEEDED" ], "errors": {} }
Despite the error, it will increase the project's pcounter (current issue number), impacting on the number of the next created tickets.
Steps to Reproduce
- Make an API call to the Create Issue V3 endpoint: /rest/api/3/issue
- Make sure the description used has more than 32767 characters
- After the failure, create a ticket via the UI and check if the ticket number is sequential
Expected Results
Error 400 - Bad Request
API fails and project's pcounter not incremented.
Actual Results
Error 400 - Bad Request
API fails and project's pcounter is being incremented.
Additional notes
The Issue ID will also be incremented alongside the pcounter
Workaround
- Add a treatment on the description to limit it to 32767 characters before making the API call
- Or use the Create Issue V2 Rest API: /rest/api/2/issue. It doesn't cause the issue.
The incrementation of the pcounter is not limited to the description limit. Any 400 received from this endpoint can result in the issue counter being incremented.
- is related to
-
JRACLOUD-77334 Jira issue creation should not increment the counter key if issue creation fails
- Under Consideration
- mentioned in
-
Page Loading...