View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0026076||mantisbt||api rest||public||2019-08-24 21:45||2019-08-25 12:36|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||2.22.0||Fixed in Version||2.22.0|
|Summary||0026076: Adding issue via REST API should fail if requested tags can't be attached|
Currently, the IssueAddCommand first creates the issue, then processes the tags.
If one or more of these tags are invalid or can't be attached for any reason, the request fails (404) as it should, but the issue has been created anyway (so the return code should be 201). Since the request is in error, it is not possible to retrieve the created issue's details.
The API call should fail without creating the issue.
|Tags||No tags attached.|
MantisBT: master b3a10d8b
2019-08-19 12:00:54Details Diff
|New method IssueAddCommand::get_tag_id()
The new method throws ClientException if the given Tag element is
invalid, thus preventing issue creation via REST API in this case.
Previously the issue would be created even though the API call was
failing with a 404 error caused by the invalid tag.
|mod - core/commands/IssueAddCommand.php||Diff File|