The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 9, 2026 11:51pm

PR Summary

Low Risk
Low risk: changes only affect error-message formatting for JSM/Jira/Confluence API failures and do not modify request/response behavior beyond returned error strings.

Overview
Improves parseJsmErrorMessage to recognize multiple Atlassian error payload shapes (single errorMessage, errorMessages[], RFC7807-style errors[], field-level errors objects, and generic message) and return the most specific message available.

Removes the hardcoded "JSM Forms API error:" prefix and falls back to returning raw errorText or ${status} ${statusText} when parsing fails or no structured message is present.

^{Reviewed by Cursor Bugbot for commit da76758. Configure here.}

Greptile Summary

This PR updates parseJsmErrorMessage in apps/sim/tools/jsm/utils.ts to handle all five Atlassian error formats (errorMessage, errorMessages[], RFC 7807 errors[].title, field-level errors object, and message), matching parity with the atlassian-errors extractor. The three JSM Forms proxy routes (forms/issue, forms/structure, forms/templates) correctly import and use this shared function, so they benefit fully from the fix. However, apps/sim/app/api/tools/jsm/request/route.ts defines its own local copy of parseJsmErrorMessage (only handling errorData.errorMessage) and does not import from utils.ts, leaving jsm_create_request and jsm_get_request error paths unchanged.

Confidence Score: 4/5

Safe to merge for Forms tools; jsm_create_request and jsm_get_request error surfacing remains incomplete.

The shared parseJsmErrorMessage in utils.ts is correctly updated and the three Forms proxy routes will benefit. However, request/route.ts still contains a local copy that only handles errorMessage, so jsm_create_request and jsm_get_request operations won't surface Atlassian error details for the four other error formats. This is a present defect in the changed surface area.

apps/sim/app/api/tools/jsm/request/route.ts — local parseJsmErrorMessage at lines 15–27 should be replaced with an import from @/tools/jsm/utils

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Executor
    participant ProxyRoute as JSM Proxy Route
    participant Atlassian as Atlassian API
    participant Utils as jsm/utils.ts (updated)

    Executor->>ProxyRoute: POST /api/tools/jsm/...
    ProxyRoute->>Atlassian: API call
    Atlassian-->>ProxyRoute: 4xx error body

    alt Forms routes (forms/issue, forms/structure, forms/templates)
        ProxyRoute->>Utils: parseJsmErrorMessage(status, statusText, errorText)
        Note over Utils: Handles all 5 formats:<br/>errorMessage, errorMessages[],<br/>errors[].title, errors{}, message
        Utils-->>ProxyRoute: Formatted error string
        ProxyRoute-->>Executor: { error: "Atlassian error detail" }
    else request/route.ts (jsm_create_request, jsm_get_request)
        Note over ProxyRoute: Local parseJsmErrorMessage<br/>only handles errorData.errorMessage
        ProxyRoute-->>Executor: { error: "JSM API error: 400 Bad Request" } stale fallback
    end

_{Reviews (2): Last reviewed commit: "fix(tools): handle all Atlassian error f..." | Re-trigger Greptile}

@greptile

@cursor review