Jira and PSA integration: how software services firms connect engineering work to billing and capacity

A Jira PSA integration lets a software services firm keep engineering work in Jira while the PSA runs the commercial side. In Birdview PSA, the Jira app imports selected projects, epics, issues, estimated hours, and assignees, one way, from Jira into Birdview. Capacity planning, time approval, budgets, and invoicing then happen in the PSA, within limits such as 600 imported issues per project.

Engineers live in Jira. Delivery leads and finance need to know who is free next month, whether a fixed-fee build is burning margin, and what to invoice on the 1st. Those questions do not have answers in an issue tracker.

Across the discovery and demo calls Birdview reviewed between March 2025 and March 2026, IT consulting firms and MSPs were the most common prospect type. The prospects already running Jira had no plan to replace it. They saw it as a developer tool, not a place to plan resources or bill clients. That split is the starting point for most IT consulting operating models, and the integration only works when the firm decides where each piece of data lives.

This article walks through one workflow, end to end, including the decisions the integration leaves to you.

Who owns what: Jira or the PSA?

Jira owns engineering execution. The PSA owns the commercial and capacity layer. Every object that matters to billing should have exactly one system of record, and the integration should only move data in the direction ownership runs.

The rule of thumb we give delivery leads is simple: never keep the same fact editable in both places. If engineers re-estimate in Jira and a project manager also adjusts the estimate in the PSA, nobody can say which number the forecast used. Pick the owner, and treat the other system as read-only for that field.

This is the same system-of-record question firms answer for CRM and accounting. Jira simply adds one more source upstream of the PSA.

What does the Birdview Jira integration sync?

The Birdview Jira app imports selected Jira projects as Birdview projects and turns their issues into activities, keeping the epic hierarchy. According to the Birdview Jira integration app help article, the current automation runs one way, from Jira to Birdview. Projects, tasks, and users created in Birdview are not sent back to Jira.

The mapping rules are fixed and not configurable. That is a feature for most firms, because nobody has to maintain a custom field map, but it also means you shape the data in Jira before import, not after.

Setup takes a few minutes. You install the app from the Atlassian Marketplace or from the Integrations tab in Birdview, connect both accounts, and tick the Jira projects to import. The person doing it needs Jira system administrator rights plus permission to manage settings and add projects in Birdview. The Jira and Birdview PSA integration page shows the screens, and the original Jira integration announcement covers the release itself.

Screenshot spec for the web team: the Manage apps screen with the Jira app, the project selection list, and an imported project showing one epic with nested stories.

How the Jira to PSA workflow runs, step by step

The workflow has six steps: agree the split, prepare Jira, import, add the commercial wrapper, capture time, then invoice and report. The example below follows an illustrative 8-week, fixed-fee build for a client portal, organized in Jira as three epics.

1. Agree the split. Before anyone installs anything, the delivery lead and the engineering lead sign off on the ownership table above. For this project, they also decide that the three epics act as billing milestones, so the epic structure in Jira must match the payment schedule in the contract.
2. Prepare Jira. Set the board’s Estimation Statistic to Time Tracking and estimate in hours. Story points will not carry over, so a team that estimates only in points arrives in the PSA with zero demand. Keep the Jira project under 600 issues, and confirm who holds Jira system administrator rights.
3. Connect and import. Select the Jira project in the Birdview app. After import, check three things: the epic hierarchy, the estimated hours on each activity, and the assignees. Imported users arrive with a Participant role and no login, so decide now who needs an active Birdview license.
4. Add the commercial wrapper in the PSA. Link the project to the client, set the billing model to fixed fee, enter the contract value, and attach a rate card for internal cost rates. Jira never sees any of this, which is the point.
5. Capture time. Engineers log billable hours against the imported activities, and a project manager approves them weekly. The next section explains why this step needs a deliberate policy.
6. Invoice and report. Birdview generates invoices from approved time and expenses under the project’s billing model, and syncs them to accounting. Budget versus actuals and margin reports update from the same approved hours.

One trade-off is worth stating plainly. Because the import runs one way, status changes, comments, and closed issues stay in Jira. The PSA tracks effort, money, and capacity. If your executives expect engineering status in the same dashboard as margin, plan for that reporting gap before go-live.

Where should billable time be captured?

Billable time should be logged in the PSA, against the activities imported from Jira. The documented field mapping covers estimates and hours left, not Jira worklogs, so time logged in Jira does not become billable time in Birdview.

Time is the link between engineering and the invoice. If it lives in two places, finance spends the last day of every month reconciling them, and the client sees a number nobody fully trusts. In the ICP calls behind this article, one operations lead at a civil engineering firm put it bluntly: invoicing took an entire day every month.

A workable policy for a Jira shop has four parts:

• One place for billable hours. Engineers keep updating Jira status, but they log hours in Birdview, on the web or the mobile app, against the same epic or story they worked on.
• Licenses for the people who log time. Jira users import as Participants without a login. Anyone who must record billable hours needs an active Birdview account.
• A weekly approval cadence. Approving 40 hours on Friday is a five-minute review. Approving 170 hours at month-end is an argument. A defined timesheet approval workflow for IT services keeps the queue short.
• No double entry. If a team insists on Jira worklogs for internal reasons, treat them as informational only, and say so in writing.

The hardest part is behavioral, not technical. Engineers already resent timesheets, and a second tool makes it worse. In the PSA rollouts we have seen, time entry compliance tends to slip after the first few weeks unless a manager reviews it weekly. The first 90 days after PSA go-live are where that habit is won or lost.

How do Jira estimates become a capacity plan?

Imported estimates and assignees give the PSA the demand side of the capacity plan; the PSA supplies the supply side from people’s working hours across all projects. Jira can tell you an epic needs 300 hours. Only the PSA can tell you whether those three engineers are also booked on two other clients that month.

Using the example project:

That 52% looks comfortable, and it is the number that gets teams into trouble. It averages the plan. In practice, Build loads three engineers heavily in weeks 3 to 6, while Discovery and Hardening leave gaps. A week-by-week view in the resource planning workspace shows where the remaining capacity actually sits, and whether sales can sell it.

The stakes are real. The 2026 SPI Professional Services Maturity Benchmark reported that average billable utilization fell to 66.4%, the lowest in the study’s 19-year history. Unsold gaps between epics are one quiet source of that number. The same benchmark found that firms using PSA software reached 70.2% utilization versus 65.0% without it.

Two practical notes. First, a Jira estimate is a single number, so add soft allocations in the PSA for work that is likely but not yet estimated, and convert them to hard allocations at sign-off; this is how teams prevent resource overbooking across clients. Second, check that allocation-based planning is included in the Birdview plan you are evaluating before you design the process around it.

How does approved time turn into an invoice?

In Birdview, invoices are generated from approved time and expenses under the project’s billing model: retainer, time and materials, or fixed fee. Jira contributes the structure and the estimates; the PSA turns approved hours into money.

The same imported project bills very differently depending on the contract:

On fixed fee work, the Jira estimate is effectively your margin assumption. If Build slips by 60 hours, nothing changes on the invoice, but the project margin does, and the budget versus actuals view is where the delivery lead should see it in week 4, not at close. On T&M work, the risk moves to unbilled or unapproved hours sitting in the queue.

Milestone billing and pool-of-hours retainers run on the same approved-time chain as automated retainer, T&M, and fixed fee invoicing on any other Birdview project. Once invoices are approved, they sync to QuickBooks, Xero, or NetSuite, so the PSA stays the source for delivery data and the accounting system receives finished invoices rather than raw timesheets.

What limits should you plan for?

The Birdview Jira app is a structured import, not a full two-way sync, and five limits shape how you use it. None of them blocks the workflow above, but each needs a decision before go-live.

If you are comparing PSA vendors, ask each one the same questions: which direction data flows and how often, whether Jira worklogs import, whether statuses map, what the issue limit is, and whether story points or custom fields carry over. Vague answers on any of these usually mean a custom API project is hiding inside the quote.

Who this setup is for

This setup fits software and IT services firms of roughly 20 to 200 people that bill clients for engineering work, keep Jira for delivery, and need capacity and margin visibility above the board. It suits fixed-fee, T&M, and retainer contracts alike. It is a weaker fit for teams that need Jira and the PSA to stay editable in both directions, or for product companies with no client billing, where Jira alone, or Jira with an internal PMO tool, is usually enough.

Making Jira and the PSA work as one system

A Jira PSA integration works when ownership is clear: Jira holds the engineering work, and the PSA holds capacity, time, and money. Import the structure once, estimate in hours, log billable time in one place, and bill only from approved hours. The integration carries the structure; the policy carries the rest.

The quickest test is a real project. Start a free Birdview trial, connect one active Jira project, and compare the imported epics and estimates against your current plan. If you want a delivery specialist to map your billing models and approval flow first, book a Birdview PSA demo for IT services teams.

FAQ

Does Birdview integrate with Jira?

Yes. Birdview’s Jira app, installed from the Atlassian Marketplace or the Integrations tab, imports selected Jira projects, issues, users, estimated hours, assignees, and dependencies into Birdview PSA for IT services teams. A Jira system administrator sets it up. The current automation runs one way, from Jira to Birdview, so changes made in Birdview do not write back to Jira.

How do Jira epics appear in Birdview?

Jira epics become top-level activities inside the imported Birdview project, not separate projects. Stories, bugs, and other issues that belong to an epic become nested activities under it, and sub-tasks nest below them. Issues that sit outside any epic appear as top-level activities beside the epics, so the Birdview structure mirrors the Jira hierarchy.

Can Jira time logs be used for billing in Birdview?

Not according to the current documentation. The Birdview Jira app imports estimated hours and hours left, but its field mapping does not include Jira worklogs. Firms that bill from Birdview have engineers log billable time in Birdview against the imported activities, then approve those hours there before they flow into invoices.

Is there a limit on how many Jira issues can sync?

Yes. In the current version, the Birdview Jira app imports no more than 600 issues per Jira project. Teams with larger projects usually split them by release, phase, or client workstream before import. Smaller projects also make fixed-fee milestones and budget tracking easier to read in the PSA.

What if my team estimates in story points?

Story points do not convert. Estimated hours import only when Jira’s Estimation Statistic is set to Time Tracking. Teams that size sprints in points can keep doing so, but should add hour estimates to billable epics or stories. Without hours, the PSA has no demand for capacity planning in Agile IT services and no baseline for fixed-fee margin.