Bug: update_ticket action creates new ticket instead of updating existing (SNT-14 → SNT-17)

[jenilv-icpl]

When trying to update an existing Jira ticket (SNT-14) using the update_ticket action via API, a new ticket (SNT-17) was created instead of updating the intended ticket.

Request Data Sent:

{
  "skip_workflow": true,
  "action": "update_ticket",
  "fields": [
    {"key": "project", "value": "SNT"},
    {"key": "ticket", "value": "SNT-14"},
    {"key": "summary", "value": "Updated summary from sungule"},
    {"key": "issuetype", "value": "Task"},
    {"key": "discrition", "value": "..."},
    {"key": "Labels", "value": "test-demo"},
    {"key": "team", "value": "ninja-team"}
  ],
  "app": "jira",
  "category": "cases"
}

Response:

{
  "success": false,
  "status": 201,
  "url": "https://infopercept-team-wpupxeuy.atlassian.net/rest/api/3/issue",
  "raw_response": {
    "body": {
      "id": "10026",
      "key": "SNT-17",
      "self": "https://infopercept-team-wpupxeuy.atlassian.net/rest/api/3/issue/10026"
    },
    ...
  }
}

Expected Behavior:

Should update ticket SNT-14.

Actual Behavior:

Created a new ticket SNT-17.

Impact:

This results in duplicate tickets being created and may confuse tracking or workflows.

Suggested Fix:

Investigate why the update flow is defaulting to a create call. Possibly validate:

• if the ticket ID is being passed to the correct endpoint (/issue/{ticketIdOrKey})
• if the action logic is properly distinguishing between update and create

[0x0elliot]

wait, is there a possibility that SN-17 is an older ticket created? Or did we hallucinate 17 out of nowhere?