Possible REST API bug, confirmation required
Answered
Hello,
I'm not sure if this is desired functionality or not but i've come across this issue and thought i should share it here before i make the assumption that it is a bug.
I'm using Youtrack InCloud with Hub Integration and I am testing the REST api via Postman (Google Extension).
Issue: If an error occurs when creating an issue, it skips one Issue ID.
How to recreate:
- Assuming the last issue of that project has an ID of Issue-8
- Create new issue via API but omit one of the required parameters such as summary. https://{name}.myjetbrains.com/youtrack/rest/issue?project={projectName}
- You will correctly get the response
{
"value": "Property [Issue: id = 90-805.summary] can't be empty."
} - Then try again with all the required parameters
- Issue is created successfully but the ID of the new issue is Issue-10.
Thanks
Please sign in to leave a comment.
Hello, thank you for your questions!
As a matter of fact, when you create issues via REST, we don't guarantee the continuity of issue IDs, but we do guarantee their consistency, i.e. there will be no issue with a smaller ID created after an issue with a greater ID.
So in your case we don't consider it a bug, it's just how this functionality works sometimes. As long as the ID numbers increase, it's as expected.
Please let us know if you have any further questions. Thank you.
Hey Liubov,
Good to know, that makes sense!
Thank you so much for the quick response :)