Resource planning for Jira teams

Jira tracks the work.
Mermix plans the people.

Still guessing who has time?

Mermix shows you: every person's work at a glance, across every project and team, around leave and their country's public holidays.

You don't have to plan alone. The copilot tells you what a plan costs, when it will likely finish and what to move.

Approve it. Push it to Jira. Get your peace of mind back.

See all features →

Built for Jira teams • Pay per resource, not per seat • EU-hosted (Frankfurt) • No credit card to start

Up and running in four steps

Connect your Jira instance, import your team, plan your schedule, and get insights. No migration, no setup calls, no spreadsheet exports.

Sound familiar?

Two audiences. Same broken process. Mermix fixes it for both.

The planner says...

The executive says...

"Marcus is leaving. I need to redistribute 14 tasks across 3 teams by Friday."

Ask the copilot. It maps capacity and proposes the reassignments in one message; you approve them and push to Jira.

"The board wants delivery risk across all portfolios. I need it by 4pm."

One message to the copilot: status per portfolio, what is overdue and who is overloaded — with a chart, and an Excel file to pass on.

"Elena's on leave next month. Which projects slip? Who picks up the slack?"

Leave and holidays are already on the calendar. The copilot shows the impact and suggests reassignments.

"How many hours actually went into PLATFORM this quarter? Finance needs numbers."

Worklogs synced from Jira. Breakdown by project, epic, and resource — exportable in one click.

"We're adding 8 tickets to the sprint. I have no idea who can take them."

Capacity heatmap shows week-by-week availability. The copilot finds the free slots and proposes the schedule.

"We have 5 teams, 4 Jira projects, and zero cross-team visibility."

Portfolio workspaces scope each team's view. One calendar shows the full picture. Nothing hidden.

The missing layer.

Jira pull to push, live capacity views to executive dashboards — everything from daily stand-up to the board report, in one place. See how Mermix handles Jira resource planning.

Mermix AI copilot — answers that span your whole plan

The copilot knows your entire plan. Ask it to rebalance work, find who has capacity, show what a plan costs and when it is likely to finish, or put a portfolio summary in an Excel file for the steering committee. It answers with tables, charts and Excel files, and every change it proposes waits for your approval.

"Redistribute Marcus's tasks across the team." "Show me delivery risk across all portfolios." "Who has capacity next sprint?" — Just ask.

Jira Pull & Push

Sync assignments and backlog items with one click. Review diffs before importing. Push date, assignee and estimate changes back to Jira when you are ready.

Drag-Drop Calendar

Schedule tasks across your whole team. Resize, reassign, and nudge bars with keyboard shortcuts. Undo any action instantly.

Capacity & Worklog Reports

12 reports across 4 dashboards — capacity heatmaps, utilisation trends, planned vs actual, profitability, and worklog detail by resource and project. Most reports export to Excel in one click.

Time-Off & Holidays

Import leave from any HR system via XLSX or CSV. Public holidays per resource country baked into every capacity calculation.

Worklog Sync

Pull Jira worklogs incrementally. Track planned vs actual hours, burn rate, and resource utilisation across all your projects.

Portfolios

Scope your workspace by team or delivery stream. Each portfolio has its own projects, resources, and planners — cross-portfolio capacity overlay included.

Pull from Jira. Review before you import.

Fetch assigned issues and backlog items from Jira in one click. Issues are grouped by status and project so you can review diffs, pick what matters, and skip the rest.

  • Two tabs: what goes on the calendar, and what goes to the backlog
  • See what's new, what's already on the calendar, and what changed since last sync
  • Field diffs shown inline — spot date or effort changes before importing
  • Each new issue says where it will land: whose calendar, which dates
  • Done issues auto-cleaned from your backlog — no stale cards
  • Sync worklogs separately for planned vs actual reporting
The Pull from Jira window listing new issues, each with the calendar and dates it will be added to

Push your plan back. Jira stays in sync.

After planning on the calendar, push date changes, reassignments, and effort updates back to Jira — selectively. Review every field change before it goes out.

  • See exactly which fields changed — dates, assignees, effort — with old vs new values
  • Grouped by project; select which tasks to push
  • Checked with Jira first: a change the connected account isn't allowed to make is unticked, with the reason
  • Success state per card — know what landed and what didn't
  • Unschedule a task, and the push clears its dates in Jira too
  • Push badge in the calendar header shows how many changes are pending
The Push to Jira drawer listing five changed tasks with the old and new dates and assignees

A calendar built for resource planning, not just events.

See your whole team's schedule at a glance. Drag tasks on the calendar or drop them straight from the backlog. Per-country public holidays and time-off render inline — so you never schedule someone during a bank holiday in another country.

  • Drag to move, resize, or reassign; drop backlog cards to schedule instantly
  • Per-country holidays and leave shown on every resource row
  • Overallocation highlighted in red — catch conflicts before they ship
  • Portfolio workspaces scope the view per team; one calendar for the full picture
  • Sprint markers, per-project colours, keyboard shortcuts, 20-step undo
The Mermix team calendar: six people, their Jira issues as coloured bars by project, and the backlog on the right

Open Mermix and see what needs you today.

The home page is a short list of what is wrong in your plan right now, each with a button that takes you to the fix. Below it, every portfolio at a glance. Board members see the same page, read-only.

  • Overdue tasks, people over capacity, work planned during leave, dependency conflicts
  • Each item opens its list in place: task, person, dates, a link to Jira
  • One click to the calendar, to the report, or to the copilot with the question already asked
  • Every portfolio: status, load for the next four weeks, share on schedule, budget used
  • Each person sees their own portfolios; an Admin also sees what is left to set up
The Mermix home page: a list of what needs attention today, each with a button to fix it, above the status of each portfolio

See who's overloaded before it's too late.

The Capacity Heatmap shows planned utilisation across your team, week by week. Spot overallocation early and rebalance workload before deadlines slip.

  • Week-by-week utilisation grid — colour-coded by load (green, amber, red)
  • Click a cell to see contributing tasks, own-portfolio and cross-portfolio
  • Team average row — instant benchmark across all resources
  • Configurable period — 4, 8, 12, or 16 weeks ahead
  • 12 reports in total — profitability, utilisation, worklogs, sync status, and more
The Capacity Heatmap report: planned load per person per week for twelve weeks, coloured green, amber and red

Stop digging through dashboards.
Just ask.

The copilot knows your entire plan — assignments, capacity, worklogs, leave, holidays, backlogs. Ask it anything about your plan. It answers with tables, charts, and Excel exports. Tell it to make a change — it proposes the action, you approve it. Nothing runs without your say-so. It works from each person's real capacity, shows what a change costs and which dates move, and tells you when there is too little data to answer instead of guessing.

For planners

  • "Redistribute Marcus's tasks — he's leaving in two weeks"
  • "Who has capacity to take on three more tickets next sprint?"
  • "Schedule the PLATFORM backlog across the team starting Monday"
  • "If Elena goes on leave next month, which projects slip?"

For executives

  • "How are we doing across all portfolios this quarter?"
  • "What has each project cost so far, and which are at risk?"
  • "Export a portfolio health summary for the steering committee"
  • "Which projects are at risk of slipping this quarter?"
The Mermix copilot answering who is overloaded, with a proposal of four changes and an Approve button

A recommendation is only as good as the data under it.

Mermix keeps your plan and Jira honest with each other, so what you decide on is what is really there.

  • Before you import: every pulled issue shows what changed and where it will land
  • Before you push: old and new values for every field, and you choose what goes
  • Checked with Jira first: changes Jira would refuse are held back, with the reason, instead of failing in Jira
  • Dependencies are the "blocks" links in Jira, read fresh when you open them
  • After each pull, tasks scheduled before the work they depend on are flagged
  • When the data is too thin, the copilot says so instead of guessing

Pay only for the people you plan.

Not your entire Jira instance. Flat monthly fee — no per-seat pricing. 14-day free trial.

Starter
€79/month

For solo PMs and small teams.

  • 25 resources · unlimited portfolios
  • Unlimited planners & projects
  • AI copilot — 150 messages/mo
Start free trial
Enterprise
€499/month

For large delivery organisations.

  • 400 resources · unlimited portfolios
  • Unlimited planners & projects
  • AI copilot — 800 messages/mo
  • 99.9% uptime target & priority support
Start free trial

14-day free trial. Every paid plan is an upgrade. Annual billing saves 20%. See full pricing →

Ready to stop guessing?

Start planning with confidence. Set up in minutes.

Get started free

14-day free trial · No credit card required · Cancel anytime