Atlassian Jira
Atlassian Jira is a comprehensive project management and issue tracking platform widely used for agile software development, task management, workflow automation, and team collaboration. Organizations use Jira to plan sprints, track bugs, manage features, coordinate releases, and monitor project progress across development teams.
| Category | IT service management |
| Direction | Query source |
| Sign-in | Email and API Token, Personal Access Token |
| Query languages | SQLite |
| Tables | 18 |
| Query templates | 55 |
| Website | atlassian.com |
Before you start
Huntbase can sign in to Atlassian Jira with any of these methods: Email and API Token, Personal Access Token. Pick one, create the credential in Atlassian Jira, then keep it to hand for the Connect step.
Email and API Token
Jira Cloud authentication using your account email (username) and an Atlassian API token.
- Sign in as the Atlassian account Huntbase should use, and go to
https://id.atlassian.com/manage-profile/security/api-tokens. - Select Create API token, enter a name, choose an expiration date, and select Create.
- Select Copy to clipboard and store the token safely. You can't recover it later.
Personal Access Token
Self-hosted (Data Center/Server) authentication using a Personal Access Token. Can only query the jira_backlog_issue
- In Jira Data Center or Server, select your avatar at the top right of the screen, then select Profile.
- Select Personal access tokens in the left-hand menu, then select Create token.
- Give the token a name and, optionally, set it to expire after a number of days.
- Copy the token before you select Close. You won't be able to see it again.
- Jira Cloud API tokens expire after one year by default, and you can set an expiry from one day up to one year.
- A Personal Access Token matches its creator's permission level, and it only supports querying issues, boards, sprints and backlog issues.
For the vendor's own instructions, see Atlassian API token documentation.
Use a dedicated, read-only credential for Huntbase where the product allows it. Huntbase only needs to read.
Connect Atlassian Jira
- Go to Connections and click New connection, or click New connection on the Atlassian Jira product page.
- On Product, pick Atlassian Jira and choose the Owner.
- On Details, give the connection a Name and, optionally, a Description.
- On Connect, fill in the settings and credentials described below.
- On Verify, review the summary and click Create & check.
For everything else on the setup page — saving a draft, I'll do this later, and what each check result means — see Connections.
Settings
Where your Atlassian Jira lives:
| Field | Required | Notes |
|---|---|---|
| Base URL | Yes | Your Jira site URL, such as https://your-domain.atlassian.net/ for Jira Cloud. |
| Username (Email) | No | The email address of the Atlassian account that owns the API token. Leave it empty when you use a Personal Access Token. |
Credentials
Choose a Method, enter a Credential label (for example Production), then fill in the fields for that method.
Email and API Token
| Field | Required | Notes |
|---|---|---|
| API Token | No | Secret — not shown again after you save it. |
Personal Access Token
| Field | Required | Notes |
|---|---|---|
| Personal Access Token | No | Secret — not shown again after you save it. |
Query it
Once connected, Atlassian Jira can serve these languages in a query tab, and Scout can use it when you ask in Auto:
| Language | Use it for |
|---|---|
| SQLite | SQL over the 18 tables listed below, alongside every other connected source. |
Example: SQLite
Jira Group Basic Info — Explore the different groups present in your Jira setup, allowing you to manage and organize users more effectively.
select
name,
id
from
jira_group;
Atlassian Jira ships with 55 query templates. Find them in Library › Queries — see Query templates.
What syncs automatically
Atlassian Jira comes with a content pack. These queries run on a schedule on each new connection so the entities they find appear in the Activity Feed without you asking. You can turn syncing off from the connection's Synchronisation Settings card.
| Query | Finds |
|---|---|
| Sync users | user |
| Sync group membership | user |
| Sync project role actors | group, user |
Tables
Atlassian Jira adds 18 tables. Browse their columns from Schema in the query bar's ⋯ menu.
All 18 tables
| Table | Contains |
|---|---|
jira_advanced_setting | The application properties that are accessible on the Advanced Settings page. |
jira_backlog_issue | The backlog contains incomplete issues that are not assigned to any future or active sprint. |
jira_board | A board displays issues from one or more projects, giving you a flexible way of viewing, managing, and reporting on work in progress. |
jira_component | This resource represents project components. Use it to get, create, update, and delete project components. Also get components for project and get a count of issues by component. |
jira_dashboard | Your dashboard is the main display you see when you log in to Jira. |
jira_epic | An epic is essentially a large user story that can be broken down into a number of smaller stories. An epic can span more than one project. |
jira_global_setting | Returns the global settings in Jira. |
jira_group | Group is a collection of users. Administrators create groups so that the administrator can assign permissions to a number of people at once. |
jira_issue | Issues help manage code, estimate workload, and keep track of team. |
jira_issue_comment | Comments that provided in issue. |
jira_issue_type | Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team’s work across your Jira site. |
jira_issue_worklog | Jira worklog is a feature within the Jira software that allows users to record the amount of time they have spent working on various tasks or issues. |
jira_priority | Details of the issue priority. |
jira_project | Project is a collection of issues (stories, bugs, tasks, etc). |
jira_project_role | Project Roles are a flexible way to associate users and/or groups with particular projects. |
jira_sprint | Sprint is a short period in which the development team implements and delivers a discrete and potentially shippable application increment. |
jira_user | User in the Jira cloud. |
jira_workflow | A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle, and typically represents a process within your organization. |
Next steps
- Connections — health, credentials and settings after you connect
- Query languages — syntax, parameters and time ranges
- Chatting with Scout — ask questions without writing a query
- All integrations — the rest of the catalog