When sending a request to the JIRA app to fetch a specific ticket (SNT-14), the app returns the entire dataset (~6500 rows), rather than filtering and returning only the requested ticket.
Request Data Sent:
{
"skip_workflow": true,
"action": "get_ticket",
"fields": [
{"key": "ticket", "value": "SNT-14"}
],
"app": "jira",
"category": "cases"
}
Expected Behavior:
Only the JIRA ticket SNT-14 should be returned in the response.
Actual Behavior:
The response includes the full dataset of tickets, which is inefficient and not aligned with the request.
Additional Notes:
- Response contains
"success": false, though HTTP status is 200.
- Likely issue with how the
get_ticket action handles the fields filter.
- Needs investigation on how filtering is applied server-side for specific ticket retrieval.
When sending a request to the JIRA app to fetch a specific ticket (
SNT-14), the app returns the entire dataset (~6500 rows), rather than filtering and returning only the requested ticket.Request Data Sent:
{ "skip_workflow": true, "action": "get_ticket", "fields": [ {"key": "ticket", "value": "SNT-14"} ], "app": "jira", "category": "cases" }Expected Behavior:
Only the JIRA ticket
SNT-14should be returned in the response.Actual Behavior:
The response includes the full dataset of tickets, which is inefficient and not aligned with the request.
Additional Notes:
"success": false, though HTTP status is200.get_ticketaction handles thefieldsfilter.