Bug: `search_tickets` with specific ticket key (SNT-14) returns all tickets instead of only the requested one

[jenilv-icpl]

Attempted to search for a specific ticket using the search_tickets action by providing the exact ticket key (SNT-14). However, instead of returning only that ticket, the API response includes a broader result set with multiple tickets.

---

Request Sent:

{
  "skip_workflow": true,
  "action": "search_tickets",
  "fields": [
    { "key": "ticket", "value": "SNT-14" }
  ],
  "app": "jira",
  "category": "cases"
}

---

Response Received:

{
  "success": false,
  "action": "search_tickets",
  "status": 200,
  "url": "https://infopercept-team-wpupxeuy.atlassian.net/rest/api/3/search?ticket=SNT-14&app=Jira%20test&action=search%20tickets",
  "output": null,
  "raw_response": {
    "body": {
      "expand": "schema,names",
      "issues": [
        {
          "expand": "operations,versionedRepresentations,editmeta,changelog,...",
          ...

---

Expected Behavior:

Should return a single ticket (SNT-14) if the exact ticket key is passed in the search_tickets request.

Actual Behavior:

Returns a full search result (similar to a general query), not limited to the ticket provided.

---

Suggested Fix:

• If the search includes a specific ticket key (e.g., SNT-14), it should either:
  • Directly hit the GET /issue/{issueIdOrKey} endpoint
  • Or construct a JQL query like: key = SNT-14

[0x0elliot]

i also notice a similar behaviour where the queries end up containing a lot of the details that was sent to singul.

ticket=SNT-14&app=Jira%20test&action=search%20tickets this bit is unnecessary.