Fetch assigned issues and backlog items from Jira Cloud. Issues are grouped by status category and project — review diffs, pick what matters, skip the rest.
Each sync fetches only issues that were updated since the previous run, per project. Even large Jira instances sync in seconds.
Made local changes and then synced again from Jira? Your edits are preserved. Mermix only overwrites a field when Jira confirms the change you pushed already landed.
When a Jira issue moves to "Done", Mermix updates it on your calendar automatically — progress marked complete, no manual action needed.
After planning on the calendar, push date changes, reassignments, and effort updates back to Jira — selectively. Review every field change before it goes out.
Changes to dates, assignees, and estimates are tracked locally. The push drawer shows a diff of every pending change. Select what to push; leave the rest.
Incrementally sync time logs from Jira into Mermix. Actual hours feed directly into capacity heatmaps, planned vs actual reports, and utilisation trends — no manual data entry.
The copilot has full context — assignments, capacity, worklogs, leave, holidays, backlogs — and goes beyond single tools. It runs multi-step plans, builds proposals, and hands them back for approval.
| Agentic skills | health_check (8-dimension quality radar) · auto_schedule (dependency-aware bin packing) · rebalance (redistribute overloaded resources) · what_if (clone-in-memory scenarios + squeeze-deadline with CPM) · executive_briefing (portfolio RAG narrative) · delta_report (changes since date) · capacity_forecast (feasibility of new work). Proposals persist 24h, preview as full Gantt overlay, import/export Excel, accept or refine in chat. |
| Analysis tools | Resource load, capacity gaps, overallocation detection, project summary, backlog breakdown, worklog queries, time-off lookup, task search, sprint data, critical path with float in working days |
| Scheduling actions | Move task, reassign, schedule from backlog, unschedule, update effort — each shown as a preview card, nothing runs without approval |
| Charts | Bar, line, doughnut, pie, sunburst, treemap, heatmap, gauge, radar, sankey — rendered inline via Apache ECharts |
| Exports | Multi-sheet Excel files generated in chat. Branded PDF export of the full conversation with charts preserved as images. |
| AI models | Haiku fast answers · Sonnet balanced · Opus deep analysis — tiered by plan |
| Credits | Monthly allowance included with every plan. Top-up packs available. Usage tracked per message, deducted only on success. |
| Role-aware | Admins and Planners get full tools. Board members get read-only analysis + sync. Engineers get personal task context. The copilot adapts automatically. |
See your whole team's schedule at a glance. Drag tasks on the calendar or drop them straight from the backlog. Each resource shows their country's public holidays and approved leave inline — so you never schedule someone during a bank holiday in another country.
Move tasks between days or between resources with a single drag. Resize bars to change dates. Drop a backlog card onto any row to schedule it instantly. Keyboard shortcuts for nudge, unschedule, and undo.
Each resource has a country code. Mermix fetches that country's public holidays and renders them as stripes on the calendar — so a Greek holiday shows on Elena's row, not on Marcus's in Germany.
A red stripe on any task bar warns you when a resource is overbooked on that day. Catch scheduling conflicts before they become delivery problems.
Approved leave shows as green stripes, pending requests as dashed amber. You see each person's availability before you schedule — no surprises.
Toggle between day-level precision and a compressed week view for big-picture planning. Bars, stripes, drag, and resize all adapt automatically.
Filter the calendar by project — unselected projects fade to ghost bars. Filter or sort resources by name. Focus on what matters right now.
Choose how many months before and after today to show. See a tight 2-month window or a wide 6-month horizon — your call.
Each portfolio scopes the calendar to its own projects, resources, and users. Planners see their team. Admins switch between portfolios or view everything at once. Cross-portfolio allocations appear as capacity overlays — so you always see a resource's full workload, even when some tasks belong to another team.
Vertical sprint lines align scheduling with sprint boundaries. Per-project colour coding makes it easy to spot which work belongs where across a busy calendar.
When someone leaves or is overloaded, open the redistribute modal — pick their tasks on the left, assign recipients on the right. Partial transfers supported. All moves are marked for Jira push.
Export the full calendar as a high-res PNG to share in presentations. The resource calendar gives each team member a personal year-at-a-glance view of their tasks, leave, and holidays.
Open the full-screen Dependency Gantt to visualise task relationships across your entire team. Click any task to select it as a predecessor, click another to link them — arrows draw instantly. Mermix also auto-detects implicit dependencies from your schedule order.
A full-screen Gantt overlay grouped by resource or project. Explicit dependencies draw as accent arrows, implicit (resource-order) ones as grey. Violated constraints turn red — catch sequencing problems before the sprint starts.
Click a task to select it as predecessor, click another to add it as successor. Choose Finish-to-Start or Start-to-Start, set an optional lag in days. Cycle detection prevents impossible graphs.
When two tasks are on the same resource in sequence, Mermix infers a Finish-to-Start dependency automatically. You can promote any implicit link to an explicit one with a single click.
Every task's modal has a Dependencies tab showing its predecessors and successors with status badges — OK, Violated, Done, or Orphaned. Add or remove links without leaving the modal.
Export the full dependency Gantt — arrows, bars, group headers, and all — as a high-res PNG. Share it in presentations, Confluence pages, or status reports.
Every capacity calculation in Mermix accounts for weekends, public holidays, and approved leave. No more accidentally scheduling someone during a bank holiday in a different country.
Each resource has an ISO country code. Mermix fetches public holidays for that country and renders them as stripes on the calendar — visible before you schedule.
Import leave from any HR system — upload an XLSX or CSV, map columns, preview matches, and import. Approved leave shows as a solid green stripe; pending as dashed amber.
Planned effort is proportionally distributed across working days only. Reports and heatmaps exclude weekends and holidays automatically — no manual adjustments.
From the one-click Executive Report for weekly PMO sessions to worklog-level detail with Cost, Revenue, and Margin on every entry. Every report exports to Excel with one click — Executive Report adds branded PDF for board decks.
Weekly PMO artifact in one click — executive summary, 12-KPI schedule grid, per-project P&L, what changed this week, next 4 weeks forward look. Branded PDF export for board decks and stakeholder emails.
Per-project P&L — actual cost from worklogs, remaining scheduled cost, projected margin against the contract sold value. Spot losing projects before they ship.
12 schedule health KPIs with sortable task-level detail and working-day variances. Spot overdue, delayed, and overallocated work at a glance.
Week-by-week utilisation grid per resource. Colour-coded green/amber/red. Click a cell to see contributing tasks.
Month-by-month capacity, planned, and actual hours. Three parallel bars per month show the full picture.
Actual hours per person with project and epic breakdown, plus Cost, Revenue, and Margin per resource using frozen T&M rates from the moment each worklog was synced. Two-sheet Excel export.
Planned, actual, and variance hours per project alongside Cost, Revenue, and Margin. The primary T&M invoice driver — rates snapshotted at sync time so historical invoices never shift.
Every worklog entry with resource, date, issue, project, epic, hours, Cost, and Revenue. Pivot by resource / project / issue for invoice line items. Margin totals per group + grand total.
Scheduled tasks with no effort estimate. Fix these first — they skew capacity and burn rate calculations.
Backlog items that haven't been placed on the calendar. Track what's waiting to be planned.
Per-project sync timestamps, worklog sync status, and all dirty tasks pending a Jira push.
Worklogs logged to your portfolio's projects by people not on the team. Catches loaned engineers, misdirected time, and unmapped Jira users.
Mermix pulls Jira worklogs using an incremental delta sync — only fetching entries added since the last run. Actual hours feed directly into planned vs actual comparisons, utilisation trends, and capacity heatmaps. No spreadsheet, no estimation, no manual calculation.
A cursor token advances after each sync. Only worklogs added after the cursor are fetched on the next run, keeping syncs fast regardless of history length.
Worklogs are resolved to their correct Epic, even for multi-level hierarchies (Task → Story → Epic). Filters by project if your team uses the project-scoped worklog setting.
Every worklog report — by resource, by project, by issue, or full detail — exports as a formatted multi-sheet Excel file. Ready for finance reviews and sprint retrospectives.
Portfolios let you scope the planning workspace by delivery team or business unit. Each portfolio has its own projects, resources, and planners — while admin users see everything and a cross-portfolio capacity overlay keeps shared resources visible across the whole organisation.
Each portfolio defines its own set of Jira projects, team members, and planner users. Switching portfolios reloads the calendar with only that team's data — no noise from other teams.
Resources shared across teams show their allocations from all portfolios as a translucent capacity layer — so you can spot conflicts and commitments without leaving your team's view.
Each portfolio can filter its own set of Jira issue types and configure its own sync lookback window — independent of the global settings. Fine-grained control without affecting other teams.
Archive completed projects to remove them from active planning. Their allocations, worklogs, and reports remain fully intact — always available for retrospectives and audits.