You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The includeAttributesDeep field in AQL GET is being interpreted as a boolean instead of an Integer.
go-atlassian version 1.14
go-atlassian component
Jira Software Cloud
Jira Agile Cloud
Jira Service Management Cloud
Confluence Cloud
Atlassian Admin Cloud
Jira Assets
Describe the bug 🐛
AQL API throws a 400 Bad Request Error due to invalid parameter.
To Reproduce 🚧
Steps to reproduce the behavior:
Call AQL API with a simple AQL query and all other parameters left empty to use defaults.
Expected behavior ✅
Return a 200 response with valid data.
Screenshots 📄
If applicable, add screenshots to help explain your problem.
Additional context
Jira Assets API notes that the includeAttributesDeep field is an integer, not a boolean. Fix is to change this type to an integer and change the formatting of the JSON message. Validated in Postman and a local change of the code.
The includeAttributesDeep field in AQL GET is being interpreted as a boolean instead of an Integer.
go-atlassian version 1.14
go-atlassian component
Describe the bug 🐛
AQL API throws a 400 Bad Request Error due to invalid parameter.
To Reproduce 🚧
Steps to reproduce the behavior:
Call AQL API with a simple AQL query and all other parameters left empty to use defaults.
Expected behavior ✅
Return a 200 response with valid data.
Screenshots 📄
If applicable, add screenshots to help explain your problem.
Additional context
Jira Assets API notes that the includeAttributesDeep field is an integer, not a boolean. Fix is to change this type to an integer and change the formatting of the JSON message. Validated in Postman and a local change of the code.
Code snippet
The text was updated successfully, but these errors were encountered: