How to Integrate Retool with JIRA

Navigate to id.atlassian.com/manage-profile/security/api-tokens in your browser. Click 'Create API token', give it a label like 'Retool Integration', and click 'Create'. Copy the token value immediately — Atlassian will not show it again after you close the dialog. This token is associated with your Atlassian account, so all Jira actions taken through it will be attributed to you. If you are setting up Retool for a team and want actions attributed to a service account, create a dedicated Atlassian account with the appropriate Jira permissions, generate the token from that account, and use that account's email in Retool. The token grants access to all Atlassian products your account can access, so treat it with the same sensitivity as a password. In Retool, you will store it as a configuration variable rather than hardcoding it in the resource settings.

In Retool, go to the Resources tab in the left sidebar and click '+ Create new resource'. Scroll through the connector list and find 'Jira' under the Productivity or Project Management category. Click it to open the configuration panel. Fill in the Name field with something descriptive, such as 'Jira (Engineering)'. For Host, enter your Atlassian domain in the format your-domain.atlassian.net — do not include 'https://' here; Retool prepends the protocol automatically. In the Email field, enter the email address associated with your Atlassian account. In the API token field, paste the token you generated in the previous step. Leave the Base path at its default (/rest/api/3/ for Jira Cloud). Click 'Test connection' — Retool will make a request to the Jira myself API endpoint to verify credentials. A successful test shows a green checkmark and your Atlassian account details. Click 'Save resource'. The Jira resource is now available in the query editor for all apps in your organization.

Open your Retool app and create a new query in the Code panel. Select your Jira resource. In the Operation dropdown, select 'Search Issues'. This reveals a JQL field where you write your search query. JQL is Jira's native search syntax — the same language used in Jira's Issue Navigator. For a basic query, enter: project = 'ENG' AND status != Done ORDER BY priority DESC. To make the JQL dynamic, reference Retool component values: project = {{ projectSelect.value }} AND status = '{{ statusFilter.value }}' AND text ~ '{{ searchInput.value }}' ORDER BY updated DESC. Add a maxResults parameter to limit the page size (default is 50, maximum is 100). If you need more fields than the default response includes, add a fields parameter listing the field IDs you want — common ones include summary, status, priority, assignee, reporter, created, updated, duedate, labels, and customfield_XXXXX for custom fields. The response includes a total count and an issues array. Name this query searchIssues and click Run to test.

1// JQL query to search issues across multiple projects
2// Reference Retool components for dynamic filtering
3
4project in ('ENG', 'OPS', 'INFRA')
5  AND status NOT IN (Done, Closed)
6  AND priority in (High, Critical)
7  AND assignee = {{ assigneeFilter.value || 'EMPTY' }}
8  AND updated >= {{ dateRange.start }}
9ORDER BY priority DESC, updated DESC

Drag a Table component from the component panel onto your app canvas. Set its Data source to {{ searchIssues.data.issues }} — note the .issues path because Jira wraps results in an outer object. In the Table column configuration, add columns for key (set type to Link to open the issue in Jira using https://your-domain.atlassian.net/browse/{{ self }}), summary, status.name (rename to 'Status'), priority.name (rename to 'Priority'), and assignee.displayName (rename to 'Assignee'). To enable status transitions from the table, create a new query using the Transition Issue operation. Set the Issue ID parameter to {{ table1.selectedRow.id }}. For the transition ID, you need to first query available transitions: create a Get Transitions query with Issue ID set to {{ table1.selectedRow.id }}, which returns the valid transitions for that issue's current status. Build a Select component that maps transition IDs to display names from the Get Transitions query result, then use the selected value in your Transition Issue query. Wire a 'Transition' button to run getTransitions first, then display the Select, and finally run transitionIssue on confirmation. On success, trigger searchIssues to refresh the table.

1// Transformer: flatten Jira issue response for Table display
2const issues = data.issues || [];
3return issues.map(issue => ({
4  id: issue.id,
5  key: issue.key,
6  summary: issue.fields.summary,
7  status: issue.fields.status?.name ?? 'Unknown',
8  statusCategory: issue.fields.status?.statusCategory?.name ?? '',
9  priority: issue.fields.priority?.name ?? 'None',
10  assignee: issue.fields.assignee?.displayName ?? 'Unassigned',
11  reporter: issue.fields.reporter?.displayName ?? '',
12  updated: new Date(issue.fields.updated).toLocaleDateString(),
13  dueDate: issue.fields.duedate ?? ''
14}));

To create new Jira issues from Retool, drag a Form component onto your canvas and add the following inputs inside it: a Select component for Project (query available projects using the List Projects operation and set options to {{ listProjects.data.values.map(p => ({ label: p.name, value: p.id })) }}), a Select for Issue Type (query using Get Issue Types for Project with the selected project ID), a TextInput for Summary, a TextArea for Description, a Select for Priority with static options (Highest, High, Medium, Low, Lowest), and a Select for Assignee (query project members). Create a new query using the Create Issue operation. Map the form fields to the query parameters: project.id to the project select value, issuetype.id to the issue type value, summary to the summary input value, description to the description textarea, and priority.name to the priority select value. In the Form's Submit event handler, trigger the createIssue query. On the query's Success event handler, add Show Notification ('Issue created: ' + createIssue.data.key) and trigger searchIssues to refresh the table. For complex integrations involving multiple Jira projects, custom field mappings, and automated Workflows, RapidDev's team can help architect and build your Retool solution.

1// Create Issue query body configuration
2// Set Operation to 'Create Issue' in the Jira native connector
3{
4  "fields": {
5    "project": { "id": "{{ projectSelect.value }}" },
6    "issuetype": { "id": "{{ issueTypeSelect.value }}" },
7    "summary": "{{ summaryInput.value }}",
8    "description": {
9      "type": "doc",
10      "version": 1,
11      "content": [{
12        "type": "paragraph",
13        "content": [{ "type": "text", "text": "{{ descriptionInput.value }}" }]
14      }]
15    },
16    "priority": { "name": "{{ prioritySelect.value }}" },
17    "assignee": { "id": "{{ assigneeSelect.value }}" }
18  }
19}