Pushing your plan back to Jira
Mermix is a two-way tool. You pull work in from Jira, plan it on the calendar, and then push your changes back so Jira stays the single source of truth for the rest of your organisation. This guide covers the push side.
How Mermix knows what changed
Every time you pull, Mermix remembers the exact values it read from Jira for each issue — its dates, assignee, estimate, and sprint. When you move a bar, reassign it, resize it, or drop it into a different sprint, Mermix compares the new value against what Jira last had. Anything that differs is pending — a change waiting to go back to Jira.
There's no "save to Jira" button to remember to press per task, and nothing is ever pushed behind your back. A badge on the Push button simply counts how many issues have pending changes.
What can be pushed
| You change in Mermix | Goes back to Jira as |
|---|---|
| Move or resize a bar | Start date + Due date |
| Drag a bar to another person | Assignee |
| Change the estimate | Original estimate (time tracking) |
| Drop a task across a sprint boundary | Sprint assignment |
| Unschedule a task you'd previously pushed | Clears the dates in Jira |
Task progress stays in Mermix. The progress slider is a Mermix-only concept for tracking how far along work is — it never writes to Jira and never counts as a pending change.
Pushing your changes
- Click Push above the calendar (or press Cmd/Ctrl + Shift + P). The Push to Jira drawer opens.
- Each pending issue is listed with a clear before → after for every field that changed — for example "24 Feb → 26 Feb" or "Unassigned → Maria".
- Tick the changes you want to send (everything is selected by default) and click Push. You'll watch each issue update in real time.
- Once an issue is pushed, its values match Jira again, so it drops off the pending list automatically.
If your calendar already matches Jira, the drawer says No local changes to push.
Throwing a change away
Unticking a task only means "not now": the change stays pending and is there again next time you open the drawer. To drop it for good, click Keep Jira's version on that task. Mermix puts the task back exactly as Jira has it (its dates, estimate, sprint and assignee) and it leaves the list. Nothing is sent to Jira.
- If Jira has the task assigned to someone who isn't on your plan, or Jira has no dates for it, it goes to the backlog with the values Jira has.
- If putting it back puts it in a dependency conflict, the drawer names the link so you can fix it on the Dependencies screen.
- Changed your mind? Close the drawer and press Ctrl + Z (Cmd + Z on a Mac) to put your changes back.
When a change can't be pushed
Mermix makes changes in Jira as the person who connected Jira, so that account's permissions in Jira apply. When the drawer opens, Mermix asks Jira what that account is allowed to change in each project. A change Jira would refuse is not ticked, can't be selected, and says why. The reason uses the names Jira gives its permissions:
| To push | The connected Jira account needs |
|---|---|
| Start date or estimate | Edit work items (Edit Issues) |
| Due date | Schedule work items (Schedule Issues) |
| Assignee | Assign work items (Assign Issues) (and the person receiving the work needs Assignable user in that project) |
| Sprint | Schedule work items and Edit work items (Schedule Issues and Edit Issues) |
| Anything at all | Browse projects |
The drawer names the account Mermix is connected with, and an Admin also sees it in Portfolios → Workspace → Jira. Ask your Jira administrator to grant the missing permission to that account in that project, then open the drawer again. Nobody needs to reconnect. To have every change appear as made by Mermix in the Jira history, create a Jira user for Mermix (for example mermix@yourcompany.com), give it these permissions, and reconnect signed in to Atlassian as that user. Everything else still pushes. The start date is a special case. Jira accepts it only if its start-date field is on that project's screens. If it isn't, or no start-date field is linked in Mermix, the drawer says so on the task: the start date stays waiting, and everything else (due date, assignee, estimate) is still pushed. Your Jira administrator can add the field to that project's screen; the "Start date" field built into Jira is usually there already.
If Jira refuses a change for another reason, the drawer shows the message from Jira and stays open so you can read it.
Push history
The drawer's Push History tab shows recent pushes — who pushed, when, and which fields moved from what to what. Handy for a quick "did that go through?" check.
Pull and push are independent
- Pull brings the latest from Jira into Mermix. Your local planning changes are preserved — a value you changed in Mermix stays until you push it, even if Jira has a different value. If Jira already has the value you set, the change is simply no longer pending.
- Push sends your Mermix changes out to Jira.
You're always in control of both directions and always shown what will change before it happens. For the pull side, see How to configure Jira for Mermix and How Mermix schedules your Jira issues.