Skip to content

Jira Extractor Setup — Customer Guide

Configure analytiQa to automatically extract issues from your Jira instance.

Prerequisites

  • Jira Cloud or Server instance (any plan)
  • Jira account with at least project member access
  • Jira API Token (from your account settings)

Step 1: Provide Your Jira URL

Tell us your Jira URL. Examples:

  • Atlassian Cloud: https://your-company.atlassian.net
  • Server/Data Center: https://jira.your-domain.com

If you're unsure, log into Jira — the URL is in your browser address bar.

Step 2: Provide Your Credentials

You need:

  1. Email address — your Jira account email
  2. API Token — generated from your Jira account

Don't have a token? See Getting Started → For Jira

Step 3: Configure What to Extract

Basic Configuration

The simplest setup extracts all issues created or updated in the last 5 days:

Created or updated in last: 5 days
Include: Comments, linked issues, custom fields
Polling interval: Every 15 minutes

Advanced Configuration (JQL Queries)

If you want specific issues, use JQL (Jira Query Language). Common examples:

Query Extracts
created >= -5d OR updated >= -5d Issues created/updated in last 5 days
status = 'In Progress' All in-progress issues
project = PROJ AND priority = High High-priority issues in project PROJ
type = Bug All bugs
assignee = currentUser() All issues assigned to you

Advanced tip: You can configure multiple JQL queries to extract different subsets of issues.

Step 4: Choose Your Polling Interval

Select how often analytiQa should check for new data:

  • Every 15 minutes (default): Good for most teams — near real-time without excessive API load
  • Custom interval: Specify a different frequency
  • Manual: Trigger extractions on-demand

Best Practice

The extraction is lightweight, read-only, and shouldn't slow down Jira — most teams leave the default interval as-is.

Step 5: Review Your Configuration

Before confirming, check:

  • ✓ Jira URL is correct
  • ✓ Email and API token are valid (analyzer will test the connection)
  • ✓ JQL queries return the data you want
  • ✓ Schedule works for your team

What Happens Next

  1. First extraction (5–30 minutes): analytiQa fetches all issues matching your JQL
  2. Daily updates (every day at scheduled time): New and updated issues are pulled
  3. Dashboard ready: Log in to analytiQa dashboard → Jira Issues tab

What Gets Extracted

From each Jira issue, analytiQa captures:

  • Basic fields: Issue key, summary, description, status, priority, type, assignee
  • Dates: Created, updated, resolved, due date
  • Metrics: Story points, time spent, estimated time
  • Relations: Linked issues, parent issues, sub-tasks
  • Comments: Full comment text and timestamps (if enabled)
  • Custom fields: Any custom fields defined in your Jira instance

Example Dashboards

Once data is ingested, see Common Queries & Reports for pre-built examples:

  • Issues by status (To Do, In Progress, Done)
  • Average resolution time by priority
  • Issue volume trends over time
  • Bugs vs. features breakdown

Troubleshooting

Issue Solution
"Invalid credentials" Check your email and API token. Generate a new token if needed.
"Connection timeout" Your Jira URL may be incorrect. Verify it in your browser.
"No data extracted" Your JQL query may be returning no results. Try a simpler query: created >= -5d
"Only some issues extracted" Your Jira account may lack permission to see all projects. Check your Jira permissions.

More help? See Support & Troubleshooting.

Next Steps