Skip to main content
Connect Jira and your tickets become build context. Rocket reads issue descriptions, acceptance criteria, epics, and sprint data directly from your board, then generates code that reflects your actual project requirements.
This connector is only available for Next.js TypeScript web build tasks.

​
What you can do

Build from a ticket

Paste a Jira issue URL into chat. Rocket reads the summary, description, and acceptance criteria, then generates the implementation.

Build from an epic

Paste a Jira epic URL. Rocket reads all child stories and the epic description, then builds the full scope.

Use sprint context

Reference your current sprint. Rocket reads active stories and priorities to understand what you are building right now.

Fix bugs from reports

Paste a bug ticket URL. Rocket reads the steps to reproduce, expected vs actual behavior, and generates a targeted fix.

Pull ticket copy into your app

Use feature descriptions, value propositions, and requirements text from tickets directly in your app’s UI.

Align code to workflows

Rocket understands Jira workflow states. It generates code that maps to your ticket statuses and transitions.

​
Connect Jira

Jira uses OAuth 2.0 via Atlassian, so no API key is needed. It is a workspace-level connector — connect it once and it is available across all tasks. The connection flow has two steps:
1

Authorize Atlassian

Authorize access to your Atlassian account.
2

Select App and Project

Select a Jira App (cloud instance) and a Project within that app.
You can connect from three places. All do the same thing.Option 1: From chatPaste a Jira ticket URL or ask Rocket to pull tickets. Rocket detects the intent and shows a Connect button inline. Click it to start the authorization flow.
Rocket chat panel showing a Connect prompt for Jira.Rocket chat panel showing a Connect prompt for Jira.

Jira connection prompt in chat

Option 2: From the Connectors tabClick the ... button in the preview toolbar, then select Connectors.
Toolbar dropdown with Connectors option highlighted.Toolbar dropdown with Connectors option highlighted.

Open Connectors from the toolbar

Click the Jira card, then click Connect.
Connectors panel showing the Jira card with a Connect button.Connectors panel showing the Jira card with a Connect button.

Jira card in the Connectors panel

Option 3: From workspace Settings

Connect from workspace Settings

Connect once from Settings and it is available across all tasks.
After clicking ConnectAn Atlassian authorization screen opens. Select your Jira cloud instance (App) from the Use app on dropdown, review the permissions, and click Accept.
Atlassian OAuth screen showing Rocket requesting access to your Jira account.

Atlassian OAuth authorization screen

After authorizing, select the Project you want Rocket to read from.A green dot appears next to Jira when the connection is active.Disconnect

Disconnect a service

Disconnect or switch accounts from workspace Settings.

​
Example prompts

Replace [JIRA_URL] with your actual issue, epic, or board URL.

​
Reading from Jira

​
Tips

  • Be specific in your tickets. Rocket builds from what is written. Tickets with detailed descriptions, clear acceptance criteria, and story points produce better output than vague ones.
  • Use issue URLs, not ticket keys alone. Pasting a direct URL gives Rocket unambiguous context. Referring to a ticket by key alone can be ambiguous across projects.
  • Scope to a single project. During connection you select one project. If you need to reference a different project, reconnect from workspace Settings.
  • Permissions apply. Rocket respects Jira’s access controls. It can only read issues and data that the connected Atlassian account has permission to access.
  • Works with Jira Cloud only. This connector uses Atlassian’s cloud OAuth. Self-hosted Jira Server and Data Center instances are not supported.

​
What’s next?

Linear

Already using Linear? Connect it for bi-directional ticket integration.

Confluence

Connect Confluence to pull product specs and documentation as build context.

GitHub

Push your code to a repository and keep version history.

All connectors

Browse every available integration.