fix(jira): add explicit fields param to search/jql endpoint

[waleedlatif1]

Summary

• Fixes Jira search issues returning empty ticket data (only id populated, all other fields blank)
• The GET /rest/api/3/search/jql endpoint requires an explicit fields parameter — without it, only the issue id is returned
• Adds fields=*all as the default in both URL construction paths when the user doesn't specify custom fields

Root Cause

The newer GET /rest/api/3/search/jql endpoint behaves differently from the older POST /rest/api/3/search — it does not default to returning all navigable fields when fields is omitted. Every other call site in the codebase (bulk_read.ts, issues/route.ts) already passes fields explicitly; search_issues.ts was the only one that didn't.

Test plan

• Run a Jira Search Issues block with a JQL query and verify all fields (key, summary, status, assignee, etc.) are populated
• Test with a JSM project to confirm service management issues return full data
• Test with custom fields parameter to verify user-specified field selection still works

[cursor]

PR Summary

Low Risk
Low risk change limited to Jira query-string construction; main risk is increased payload size or hitting Jira response limits when defaulting to *all.

Overview
Fixes Jira issue searches returning mostly empty issue objects by always sending a fields parameter to the GET /rest/api/3/search/jql endpoint.

When callers don’t provide fields, search_issues.ts now defaults to fields=*all in both the direct URL builder and the transformResponse-initiated follow-up search.

^{Written by Cursor Bugbot for commit 0a69f1a. Configure here.}

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 12, 2026 7:51pm

[greptile-apps]

Greptile Summary

This PR fixes a bug where the Jira Search Issues tool returned tickets with only the id field populated. The root cause is that the newer GET /rest/api/3/search/jql endpoint does not default to returning all navigable fields when fields is omitted — unlike the older POST /rest/api/3/search endpoint.

Key changes:

• In both URL-building paths (request.url and performSearch inside transformResponse), the existing if branch that sets user-specified fields is extended with an else branch that defaults to fields=*all.
• The fix is minimal, consistent, and aligns search_issues.ts with how other Jira tool files (bulk_read.ts, issues/route.ts) already handle field selection.
• The * character is preserved as-is by URLSearchParams, so no encoding issue arises.

Confidence Score: 5/5

• This PR is safe to merge — it is a focused, low-risk bug fix with no structural changes.
• The change is a two-line else-branch addition in two symmetric places. It correctly addresses the documented root cause, is consistent with the rest of the codebase, and carries no risk of regression beyond slightly larger API payloads (due to fetching all fields by default).
• No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/tools/jira/search_issues.ts	Adds fields=*all as the default in both URL construction paths (request.url and performSearch) when the user provides no custom fields, fixing the empty-data bug with the GET /rest/api/3/search/jql endpoint. Only a minor doc inconsistency (param description still says "all navigable") needs updating.

Sequence Diagram

sequenceDiagram
    participant Client
    participant Tool as jiraSearchIssuesTool
    participant Atlassian as Atlassian API

    Client->>Tool: call(params)

    alt cloudId provided
        Tool->>Atlassian: GET /ex/jira/{cloudId}/rest/api/3/search/jql?jql=...&fields=*all
        Atlassian-->>Tool: { issues: [...], nextPageToken, isLast, total }
    else cloudId not provided
        Tool->>Atlassian: GET /oauth/token/accessible-resources
        Atlassian-->>Tool: [{ id: cloudId, ... }]
        Tool->>Atlassian: GET /ex/jira/{cloudId}/rest/api/3/search/jql?jql=...&fields=*all
        Atlassian-->>Tool: { issues: [...], nextPageToken, isLast, total }
    end

    Tool->>Tool: transformSearchIssue(issue) for each issue
    Tool-->>Client: { success: true, output: { issues, nextPageToken, isLast, total } }

Loading

Comments Outside Diff (1)

1. apps/sim/tools/jira/search_issues.ts, line 121 (link)

   Stale param description after default change

   The fields parameter description still says "default: all navigable", but the code now defaults to *all (all fields, including non-navigable). This could mislead users who rely on the description to understand the tool's behavior.

_{Last reviewed commit: 0a69f1a}