--- title: "Jira channel" slug: "jira-channel" updated: 2026-04-27T19:24:40Z published: 2026-04-27T19:24:40Z --- > ## Documentation Index > Fetch the complete documentation index at: https://help.quickbase.com/llms.txt > Use this file to discover all available pages before exploring further. # Jira channel > *Go to the*[*Channels*](https://team.quickbase.com/nav/main/action/pipelines/channels)*page to learn more about what plans have access to this channel. Sign into Quickbase, and then go to Pipelines > Channels.* Jira is an issue tracking product developed by Atlassian that allows bug tracking and agile project management. For information about connecting with Pipelines Agent, see [Quickbase Pipelines Agent connections](/v1/docs/quickbase-pipelines-agent-connections). **Note**: For the sprint information to be displayed, the field **Issue type** must be completed. Terms used in the Jira channel categories are Jira-specific terminology. ## How to connect 1. On the My pipelines page, select **Create Pipeline**. 2. Search for or select a step, and then select it to add it to the pipeline. When you add a step to a pipeline, it is added to the canvas of the pipeline designer. 3. Expand the Connection section of the step, and add the required information. ### Connect to Jira 1. Enter your organization's URL, your Username and Password, or API token **Note**: An API token can only be used if your Jira instance is cloud-based. If you are unsure if Jira is cloud-based or locally hosted, check with your Jira administrator. 2. Optionally, enable the following settings if needed: - Have a proxy connection via an on-premises agent - Disable SSL certificate verification - Connect to a Jira Cloud instance that uses a custom domain, for example any domain that doesn't end with .atlassian.net 3. Select **Connect** ## How to reconnect You may need to reconnect your account to a channel. Reasons may be (but not limited to): - If you need to connect a different account. - Authorization updates, such as a changed password. - Editing the access rights that Pipelines has to the channel. To reconnect: 1. Select a pipeline that already has this channel in it. 2. Open a step that contains this channel. 3. Under account, select **Connect (or reconnect)** and follow the process above, [How to connect](/v1/docs/jira-channel#how-to-connect). ![The Connect (or reconnect) button in the Connection section of a pipeline step](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/17563880008468.png) ## Steps The steps you can use with Jira are grouped into five categories: - Comments - Issues - Worklogs - Attachments **Note:** You cannot use jinja expressions in trigger conditions unless explicitly specified as possible. | Type | Name | Description | | --- | --- | --- | | Comments | | | | Trigger | Comment Created | Triggers when a new comment is created in the selected project. | | Trigger | Comment Updated | Triggers when a comment is updated in the selected project. | | Action | Comment on an Issue | Creates a new comment to the selected issue. | | Action | Update Comment | Updates a comment in a specific issue. | | Query | Search Comments | Searches comments and returns a list. | | Action | Fetch a Linked Comment | Fetches a linked comment. | | Action | Look Up Comment | Searches comments and returns a single record. | | Issues | | | | Trigger | Issue Created | Triggers when a new issue is created in the selected project. If a project is not selected all issues in all projects are monitored for updates. | | Trigger | Issue Updated | Triggers when an issue is updated in the selected project. If a project is not selected all issues in all projects are monitored for updates. | | Action | Create Issue | Creates an issue in the selected project. | | Action | Update Issue | Updates the selected issue. | | Action | Transition Issue | Transitions the selected issue to another state. | | Action | Delete Issue | Deletes the selected issue. | | Action | Add Watcher | Adds a watcher to the issue. | | Action | Remove Watcher | Removes a watcher from the issue. | | Query | Search Issues | Searches a project and returns a list of issues. | | Query | Search Subtasks | Lists subtasks of an issue. | | Action | Fetch a Linked Issue | Fetches a linked issue. | | Action | Look Up an Issue | Fetches an issue by uniquely identifying attribute. | | Worklogs | | | | Trigger | Worklog Created | Triggers when a new worklog entry is created in an issue. | | Trigger | Worklog Updated | Triggers when a worklog is updated. | | Attachments | | | | Trigger | Attachment Created | Triggers when an attachment is created. | | Trigger | Attachment Deleted | Triggers when an attachment is deleted. | | Action | Create Attachment | Creates an attachment. The file limit is 100 MB. | | Action | Delete Attachment | Deletes an attachment. | | Query | Search Attachments | Searches attachments and returns a list. | | Action | Fetch a Linked Attachment | Fetches a linked attachment. | | Action | Look Up Attachment | Looks for an attachment and returns a single record. | | Projects | | | | Trigger | Project Created | Triggers when a project is created. | | Trigger | Project Updated | Triggers when a project is updated. | | Query | Search Projects | Searches projects and returns a list. | | Action | Look Up project | Looks for a project and returns a single record. | ## Use cases Here are some use case examples to help you understand how to use the Jira channel. In this example, when a Quickbase form is completed, a Jira ticket is created. 1. We add a **Quickbase Record Created** step to trigger when a new help feedback form is completed. 2. Then we add a **Jira Create an Issue** action that takes data from the Quickbase form and creates a Jira ticket to review the feedback.