> ## Documentation Index > Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt > Use this file to discover all available pages before exploring further. # Connect your app to Jira > Connect your app to Jira, Atlassian's issue and project tracker, by signing in with your Atlassian account to search, create, and update issues. [Jira](https://www.atlassian.com/software/jira) is Atlassian's issue and project tracker for software and business teams. The Jira connector lets your Lovable app search, create, and update issues on your Jira Cloud site and read its projects, boards, and sprints. | Use | If you want to | | - | - | | **App + chat connector** (this page) | Work with a shared Jira connection in Chats, in the project chat while you build, and in your published apps | | [Chat connector (MCP server)](https://docs.lovable.dev/integrations/chat-connectors.md) | Let Lovable read your own Jira issues and Confluence pages as context while you build, personal to you | With Jira, your app can: * Search issues with JQL (Jira Query Language) and count matching issues * Create and update issues, add comments, and assign people * Move issues through their workflow and link related issues * Read epics, subtasks, and an issue's status history * Log work and read work logs * Read projects, boards, and sprints Your app acts as the connected Atlassian account. Issues it creates list that account as the reporter, and comments and work logs list it as the author. A bug report form therefore files every report under the connected account's name, not the submitter's. It's a good fit for sprint dashboards, bug and feedback intake forms, triage views, and reporting tools for teams that already track work in Jira. ## Common use cases and example apps These examples show what you can build with Jira, each with a prompt to start from. | Example app | Example prompt | Description | | :- | :- | :- | | Sprint dashboard | *Use Jira and build a dashboard that shows the active sprint for our `ABC` board, with issues grouped by status and assignee.* | **See sprint progress without opening Jira.** The app reads the board's active sprint and its issues, and groups them by status and assignee. | | Bug report form | *Use Jira and build a bug report form that creates a Bug in project `ABC` with the reporter's description and steps to reproduce.* | **Turn form submissions into Jira issues.** The app creates an issue in the project you choose, with the description formatted as Jira rich text. | | Triage workspace | *Use Jira and build a triage view that lists new unassigned issues in project `ABC` and lets me set priority, assign, and move them to To Do.* | **Review and route incoming work from one screen.** The app searches with JQL, updates fields, assigns people, and moves issues to the next workflow status. | | Customer feedback portal | *Use Jira and build a feedback portal where customers submit requests, and each request becomes a Jira issue with a public status page.* | **Collect feedback and show customers where it stands.** The app creates an issue for each request and reads its status back to show progress. | | Cycle time report | *Use Jira and build a report that shows how long issues in project `ABC` spent in each status over the last 30 days.* | **Measure how work moves through your workflow.** The app reads each issue's status history and calculates time spent per status. | | Timesheet | *Use Jira and build a timesheet where I log hours against my assigned issues and see my total for the week.* | **Log time against Jira issues from a simpler view.** The app lists your assigned issues, adds work logs, and sums the week's logged time. | ## How to connect Jira Who can create Jira connections depends on your plan and workspace settings. App + chat connectors are available by default. On Business and Enterprise plans, [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients) starts at **Admins**. Some Enterprise workspaces start at **No one**, which disables the connector. An admin or owner changes it in **Connectors → Admin settings → App + chat connectors**. You can create multiple Jira connections using different Atlassian accounts or Jira sites, which is useful for separating environments or working with more than one site. When the connection is created, you can [link it to the projects](https://docs.lovable.dev/integrations/app-connectors.md#link-a-connection-to-a-project) where you want to use it. Anyone building in a project can ask Lovable in chat to link their project to it. ### Prerequisites Before connecting Jira, make sure you have: * A Jira Cloud site, with an address such as `mycompany.atlassian.net` * An Atlassian account with access to that site * Permission to **create connections** in your Lovable workspace (see [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients)) > [!NOTE] > > All API requests made through this connector count against Atlassian's Jira Cloud rate limits. Billing and quota are handled directly by Atlassian, not Lovable. ### Set up your Jira connection You authorize Lovable with your Atlassian account, and no API token is needed. **1. Open Jira in Connectors** Open [**Connectors**](https://lovable.dev/dashboard?connectors) and select **Jira**. For the other places to open the catalog from, see [Where to find connectors](https://docs.lovable.dev/integrations/introduction#where-to-find-connectors). **2. Add a connection** Click **Connect** on the connector page. The form is split into collapsible sections, **Details**, **Configure connection**, and **Sharing**. **3. Name the connection** Under **Details**, Lovable fills in a name for the connection, which you can change. The name is only used inside Lovable to identify the connection. **4. Enter your Jira site** Under **Configure connection**, enter your Jira Cloud address in **Jira site**, for example `mycompany.atlassian.net`. You can also paste any Jira URL from that site. The site cannot be changed after the connection is created. To use another site, create another connection. **5. Review scopes (optional)** Under **Scopes**, review the permissions your app requests. **Read Jira work** and **Stay connected** are always included. The other read scopes and **Write Jira work** are selected by default. Scopes that manage or delete projects and sprints are off by default. | Scope | Description | Default | | - | - | - | | Read Jira work (`read:jira-work`) | Read projects, issues, comments, work logs and search with JQL. | Required | | Stay connected (`offline_access`) | Keep the connection working after the first hour without signing in again. | Required | | Write Jira work (`write:jira-work`) | Create and update issues, comments and work logs, and transition issues. | On | | Read users (`read:jira-user`) | Look up users, assignees and the connected account. | On | | Read boards (`read:board-scope:jira-software`) | Read boards and backlogs. | On | | Read sprints (`read:sprint:jira-software`) | Read sprints and their issues. | On | | Read projects (`read:project:jira`) | Read project details. Boards need it too. | On | | Read issues on boards and sprints (`read:issue-details:jira`) | Read the issues on a board, backlog or sprint. | On | | Search sprint issues (`read:jql:jira`) | Filter the issues in a sprint with JQL. | On | | Manage projects (`write:project:jira`) | Create and update projects. | Off | | Delete projects (`delete:project:jira`) | Delete projects and their issue types, leads and avatars. | Off | | Move issues on boards (`write:board-scope:jira-software`) | Move issues between backlogs and boards. | Off | | Manage sprints (`write:sprint:jira-software`) | Update sprints, order them and move issues into them. | Off | | Delete sprints (`delete:sprint:jira-software`) | Delete sprints and their properties. | Off | For full scope documentation, see [Atlassian's Jira scope reference](https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/). **6. Choose who can use this connection** Under **Sharing**, the connection is private to you by default and shows a **Private** label. To share it, click **Share with others**. Then add workspace members by email, or click **Invite entire workspace** to make the connection available to everyone in your Lovable workspace. Everyone you share the connection with sees the projects and issues the connected Atlassian account can see. See [Who can use connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-use-connections-and-clients) for more information. **7. Connect to Jira and authorize** Click **Connect** at the bottom of the form. The Atlassian authorization window opens, so make sure your browser doesn't block pop-ups. If it does, Lovable redirects you instead. Sign in to Atlassian if prompted. On the consent screen, choose the same site you entered in **Jira site**, review the requested permissions, and click **Accept**. You'll be redirected back to Lovable with a confirmation. When connected, anyone building in a project can ask Lovable in chat to link their project to Jira (based on configured connection-level access). Your Lovable apps can then search, create, and update issues on your Jira site within the scopes you approved. ## Limitations The Jira app + chat connector documented on this page cannot: * Connect to Jira Server or Jira Data Center. Only Jira Cloud sites (`*.atlassian.net`) are supported. * Reach more than one Jira site per connection. * Call Confluence, Jira Service Management request APIs, or Marketplace apps with their own APIs, such as Xray or Tempo. * Receive Jira webhooks. * Support per-end-user Jira login. Each connection represents a single Atlassian account shared across all projects linked to it. ## Troubleshooting Use these checks when connecting fails or a Jira request returns an unexpected status. > [accordion] The connection fails after you authorize > > The Atlassian account did not grant access to the site you entered in **Jira site**. This happens when you choose a different site on the Atlassian consent screen, or when the account has no access to that site. Create the connection again, and on the consent screen choose the site you entered. > [accordion] The connection shows an Expired badge > > Atlassian ends the sign-in when the connection goes unused for 90 days. Open the connection and click **Reconnect** to sign in again. > [accordion] Requests fail with a message to reconnect Jira > > The Atlassian account lost access to the site you entered, or Atlassian now identifies that site differently, for example after a site migration. Access is lost when someone revokes the app in the Atlassian account settings or removes the account from the site. Open the connection, click **Reconnect**, and on the consent screen choose the site you entered. ## Manage your Jira connection Connections are managed from [**Connectors**](https://lovable.dev/dashboard?connectors): select **Jira**, then open the connection. * **Unlink projects** to remove Jira access from specific projects while keeping the connection available for others. See [Unlink projects from a connection](https://docs.lovable.dev/integrations/app-connectors.md#unlink-projects-from-a-connection) for the steps. * **Delete the connection** to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use Jira stop working until a new connection is added. See [Delete a connection](https://docs.lovable.dev/integrations/app-connectors.md#delete-a-connection) for the steps and who can delete.