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 to Jira (or press Cmd/Ctrl + Shift + P). The push 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 just tells you everything is in sync — there's nothing to push.
Push history
The drawer keeps a short history tab so you can see 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 Jira's latest into Mermix. Your local planning changes are preserved — Mermix won't silently overwrite a date you've set until you either push it or pull a newer value from Jira for that same field.
- 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.