Jira + Orcabase

How long does work really take?

Sync Jira through Fivetran and ask how long issues take, where they wait and how much of each sprint goes to bugs, in plain words, without building another Jira dashboard.

Get started How to connect

Synced by Fivetran
Syncs every 6 hours
No Fivetran account needed

AgentJira connected

How long do bugs take from report to fix?

Reading your Jira data…

Bugs took 9 days from report to fix in August, down from 14 in April.

Most of that time is spent waiting in “To do”: 6 days.
Bugs reported by customers are fixed twice as fast.
A few old bugs pull the average up: the median is 4 days.

Days from report to fix, by month

How I got this· 4 steps

Looked at your Jira issues and their history
Kept bugs fixed each month
Measured days from created to done
Split the time by status

Example answer. Numbers are illustrative.

In plain words

How do I measure cycle time in Jira?

Cycle time needs every status change, not just where issues are today. Fivetran copies your Jira issues and their full history into a database Orcabase hosts for you, so time in each status can be measured.

Ask “where do issues wait longest?” and get the answer with a chart, and next to the support tickets those bugs caused.

Ask in plain words

What you can ask about your Jira data

The agent answers with the number, a chart and the steps it took. Keep the good answers on a dashboard.

Meet the data agent

How long do bugs take from report to fix?
How much of each sprint went to bugs?
Where do issues wait longest?
How many issues did each team finish this quarter?
Which epics are behind?
How many issues were carried over from the last sprint?
Which components get the most bugs?
Show me issues created and resolved by week.

What comes in

Your Jira data, ready to ask about.

A copy in a database Orcabase hosts for you, with its own folder for each app.

Issues

Every issue, with its type, status, priority, assignee and fields.

Issue history

Every status change, so time in each status can be measured.

Projects and components

How your work is organized.

Sprints

What was planned, finished and carried over.

Versions

Releases, and the issues in each.

Worklogs

Time logged against issues, if your team logs it.

Numbers worth defining

Define them once. Every answer agrees.

Tell Orcabase what each number means, certify it, and your dashboards, the agent and your whole team use the same one. The agent can draft these from your Jira data.

How metrics work

Cycle time
Days from work starting on an issue to done.
Lead time
Days from an issue being created to done.
Bug share
Share of finished issues that were bugs.
Carry-over
Share of a sprint’s issues left unfinished at its end.

Dashboards to start with

Your Jira numbers at a glance.

Ask the agent to build one of these, or pin charts yourself. Share any dashboard with a link.

Delivery

4 charts

Issues done by week
Cycle time
Bug share by sprint
Carry-over

Quality

3 charts

Bugs created vs fixed
Days from report to fix
Bugs by component

About dashboards

Better together

Ask across Jira and the rest of your business.

The best questions need more than one app. The agent can pull from several sources for one answer.

“Which bugs cause the most support tickets?”

Jira + Zendesk

“How long do issues wait between the last commit and done?”

Jira + GitHub

“Did last quarter’s releases change how many customers upgrade?”

Jira + Stripe

How to connect

Connect Jira, step by step.

1
Find it in Sync data
In Orcabase, go to Sync data → Add source and search for Jira. Pick the database to sync into.
2
Connect Jira on Fivetran’s page
Fivetran’s page asks you to sign in to Jira, or for an API key. Your login goes to Fivetran, never to Orcabase.
3
Choose what to sync
Back in Orcabase, tick the data you want. Only what you pick is synced, and only it counts toward your allowance.
4
Ask away
The first sync starts straight away. When it’s done, ask the agent about your Jira data.

What you’ll need

A Jira login that can see the projects you want to sync.
The Admin role in Orcabase, and data hosting: Fivetran writes into a database Orcabase hosts for you.

At a glance

How it connects: Synced by Fivetran
How fresh: Every 6 hours, as standard.
Where your data lives: A copy in a database Orcabase hosts for you, with its own folder for each app.
Who can set it up: An admin in your organization.
Your login: You sign in on Fivetran’s own page. Orcabase never sees your password or keys.
Cost: Counts toward your monthly sync allowance: 500,000 changed rows a month, as standard.

Sync apps with FivetranStep-by-step, in the docs.

Questions

About Jira and Orcabase

More in the docs: Sync apps with Fivetran

Can I measure time in each status?

Yes. Every status change comes along, so the agent can measure how long issues wait in each one.

Can Orcabase change issues?

No. Orcabase only reads the synced copy.

Do I need a Fivetran account?

No. Orcabase uses its own. You sign in to Jira on Fivetran’s page, and the data lands in a database Orcabase hosts for you, so there’s nothing else to set up or pay Fivetran for.

How fresh is my Jira data in Orcabase?

Fivetran syncs it every 6 hours as standard, and an admin can run a sync by hand at any time. The page for each source shows when it last synced and when it syncs next.

What does syncing cost?

Counts toward your monthly sync allowance: 500,000 changed rows a month, as standard. Each distinct row that’s added or changed in a month counts once, however often it changes, and the first full copy is free. You choose which tables sync, so you only spend the allowance on what you need.

Keep exploring

More data sources

All data sources

Your Jira data already has the answers.

Connect it, ask your first question, and pin the answers you want to see every week.

Get started All data sources