← All guides

Getting started with Mermix

Mermix turns the work already in your Jira into a drag-and-drop plan for your team. You connect Jira, Mermix pulls in your issues and the people they're assigned to, and you get a live capacity calendar you can adjust — then push your changes back to Jira. This guide takes you from sign-up to your first plan in about five minutes.

1. Create your workspace

  1. Sign up at mermix.io. Pick a workspace name — this becomes your web address (your-team.mermix.io) and can't be changed later, so choose the name you'll keep.
  2. Check your inbox and click the verification link. It opens the setup wizard; your workspace is created when you finish it.

Bookmark your workspace URL or keep the welcome email — it's how you get back in. If you ever lose both, you can recover it at mermix.io/find-workspace.

No credit card is required to start. You begin on a 14-day free trial — see The 14-day trial.

2. Connect Jira

The setup wizard walks you through connecting Jira with Atlassian's secure OAuth flow — you log in to Atlassian and approve access; Mermix never sees your Atlassian password. You then choose:

  • Which projects to sync (up to three in the wizard — you can add more later in Portfolios → All projects).
  • Which issue types to plan — Story, Bug, and Task are selected by default. Epics are used to group work, not scheduled individually.

If your Jira has no start-date field Mermix can use, the wizard says so on its last step and what your Jira administrator can do; you can finish setup and fix it later. Full detail: How to configure Jira for Mermix.

3. Run your first sync

The wizard runs the first sync automatically. Mermix reads each issue's assignee, dates, and estimate and decides where it belongs:

  • Issues with an assignee and enough date/effort information land on the calendar.
  • Everything else lands in the backlog, ready for you to schedule.

A summary tells you exactly how each issue was placed. The full logic is explained in How Mermix schedules your Jira issues.

Your trial clock starts on this first sync — not at sign-up — so you get the full 14 days to actually evaluate Mermix with real data.

4. Plan your team

You're now looking at your team's calendar — one row per person, coloured bars for their work, with weekends shaded and thin stripes for public holidays and time off.

  • Drag a bar to move it, drag its edges to resize, or drag it to another person's row to reassign.
  • Drag an issue from the backlog onto the calendar to schedule it.
  • A red stripe on a bar means that person is overbooked on at least one day it covers.
  • Press Cmd/Ctrl + K any time to ask the AI copilot to analyse workloads, find a free slot, or make changes for you.

Every change you make is tracked as a difference from Jira. When you're ready, push it back to Jira in one place.

5. Invite your team (optional)

In Portfolios → All people, give teammates a login with the role that fits — from the ⋯ menu on their row, or Add a login for someone who is not scheduled. They get an email with a link to choose their own password.

Role What they can do
Admin Everything in the workspace — setup, logins, planning.
Planner Full read/write planning, reports, and the AI copilot.
Board Views the portfolios, Team Calendar, Dependencies and reports, and asks the copilot; exports "Who's doing what" and pictures. Changes nothing. Free and unlimited.

Engineers don't need a login: they keep working in Jira. When you push the plan, Mermix writes each task's dates and assignee to Jira, so they see their assignments in their stand-ups and in the Jira calendar.

What's next

Stuck on anything? Ask the copilot (Cmd/Ctrl + K) or email hello@mermix.io.