> ## Documentation Index > Fetch the complete documentation index at: https://docs.noxus.ai/llms.txt > Use this file to discover all available pages before exploring further. # Jira > Start flows from new, updated and commented Jira work items, and list, create, update, transition, assign, link and comment on work items, projects and users Use Jira to start a flow when work items change in a project, and to work with work items, projects and users from inside a flow. This flow assigns every new bug in the Support project to triage and tells the reporter. Press **Run** to watch it. Node Output in this run Every trigger and node needs a Jira connection. See [Connect Atlassian](https://docs.noxus.ai/integrations/providers/atlassian.md) to set one up. ## Triggers All three triggers check the project every minute. Only work items and comments created or changed after you turn the trigger on start a flow: what was already in Jira never does. A check starts at most 50 runs, and the rest start on the next check. What it does ## Nodes | Node | What it does | | - | - | | [List Work Items](#list-work-items) | Lists the work items in a project, newest first | | [Get Jira Work Item](#get-jira-work-item) | Gets one or more work items by key | | [Create Work Item](#create-work-item) | Creates a work item | | [Update Work Item](#update-work-item) | Changes a work item's fields | | [Transition Work Item](#transition-work-item) | Moves a work item to a new status | | [Assign Work Item](#assign-work-item) | Assigns or unassigns a work item | | [Link Work Items](#link-work-items) | Links two work items | | [Add Jira Comment](#add-jira-comment) | Comments on a work item | | [Get Jira Comments](#get-jira-comments) | Reads a work item's comments | | [Add Jira Attachment](#add-jira-attachment) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Attaches files to a work item | | [Search Jira Users](#search-jira-users) | Finds users by name or email | | [Create Jira User](#create-jira-user) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Creates a user and invites them by email | | [List Jira Projects](#list-jira-projects) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Lists the projects the connection can see | | [Get Project Info](#get-project-info) | Gets a project's details and work item types | | [Create Jira Project](#create-jira-project) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Creates a project | | [Update Jira Project](#update-jira-project) [From 1.11.0](https://docs.noxus.ai/core/changelog.md#1-11-0) | Changes a project's name, lead or description | Where a node asks for a user, such as **Assignee** or **Lead**, enter their email or their account ID. What it does ## Troubleshooting > [accordion] A work item did not start the trigger > > Only work items and comments created or changed after the trigger was turned on start a flow. Check the **Project** and **Work item type** filters. With **Ignore changes made through this connection** on, changes made by the connection's account are listed in the trigger's events as `Made through this Jira connection`. > [accordion] Could not read the Jira account's time zone... > > The trigger reads the connection account's time zone to search Jira. Set a time zone on that Atlassian account, then check the trigger again. > [accordion] More than 10000 Jira work items changed within 10 minutes... > > Too many work items changed at once for the trigger to tell which are new. Narrow it with **Work item type**, or watch a smaller project. > [accordion] Could not fetch ... (not found in Jira) > > A key in **Work item keys** does not exist, or the connection cannot see it. Keys marked `invalid key format` are not shaped like `SUP-42`. The other work items are still returned. > [accordion] Transition ... not found for issue ... > > The work item cannot move through that transition from its current status. The message lists the transitions it can take; pick one of those. > [accordion] Transition ... was accepted by Jira but issue ... is still in ... > > Jira accepted the transition, but the work item did not show the new status in time. Check the work item's history in Jira. > [accordion] Could not find exactly one Jira user for ... > > The email matches no user, or more than one, or Jira hides that user's email. Enter the user's account ID instead. > [accordion] Cursor must be the next\_cursor of a previous run > > Bind **Cursor** to `next_cursor` from a List Work Items node with the same settings, or leave it empty to start from the first result. > [accordion] Set a new name, lead or description to update the project > > Update Jira Project needs at least one of **Name**, **Lead** or **Description**. > [accordion] Failed to attach ... Already attached: ... > > Some files were attached before one failed. Running the node again attaches those files a second time, so remove them from **Files** first. > [accordion] ... Jira returned HTTP 403... > > The connection's account lacks permission for this project or action. Create Jira User needs Jira admin rights. See [Connect Atlassian](https://docs.noxus.ai/integrations/providers/atlassian.md). > [accordion] Could not reach Jira... > > Check the **Jira URL** on the connection. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.