What Mermix can see and change in Jira
When you connect Jira, Atlassian shows a consent screen listing what Mermix asks to do. The wording on that screen is Atlassian's, and it describes everything a permission allows, not what Mermix does with it. This page explains each item in plain words, so you know what you are approving.
Mermix acts in Jira as the account that connected it. It can never do more than that account is allowed to do in your projects. See Before you start for the permissions that account needs.
What Mermix asks for, and why
| Atlassian permission | What Mermix uses it for |
|---|---|
Read Jira work (read:jira-work) |
Reads your projects, issue types, work items, their dates, estimates and assignees, logged time, "Blocks" links and status history. Also checks what the connected account is allowed to do, so the Push drawer can tell you before Jira refuses a change. Atlassian's description also mentions comments, attachments, watchers and votes: Mermix reads only what is listed here. |
Update work items (write:issue:jira) |
Sends your plan back when you push: start date, due date, estimate and assignee. Atlassian describes it as "create and update issues"; Mermix never creates a work item. |
Add and remove links (write:issue-link:jira, delete:issue-link:jira) |
Adds or removes a "Blocks" link when you change a dependency in Mermix. |
Comments (write:comment:jira) |
Not used. Atlassian requires it for any app that adds a link, because adding a link can also post a comment. Mermix never sends one. |
Read Jira users (read:jira-user) |
Lists the people on your site so you can import your team, and names the account Mermix is connected with. An email address is visible only if that person's Atlassian profile shows it to everyone. |
Read boards and sprints (read:board-scope:jira-software, read:sprint:jira-software) |
Shows sprint badges on the backlog and sprint lines on the calendar. |
Write sprints (write:sprint:jira-software) |
Moves a work item into the sprint its new dates fall in, when you push. |
Read projects and work item details (read:project:jira, read:issue-details:jira) |
The parts of reading projects and work items that the board and sprint features in Jira require separately. |
Stay connected (offline_access) |
Keeps the connection working when nobody is signed in to Mermix, so Mermix can tell your Admins when the connection is lost, and report to Atlassian that it still holds people's details, as Atlassian requires of every app. |
When Mermix changes anything in Jira
Only when someone in your workspace decides to:
- Push: a planner opens the Push drawer, sees each change, and sends the ones they tick.
- Dependencies: a planner adds or removes a dependency on the Dependencies screen.
- AI copilot: every change the copilot proposes waits for a planner's approval. Date and assignment changes then reach Jira with the next push; an approved dependency change is written to Jira straight away.
Pulling from Jira only reads.
What Mermix never does
- Change your Jira configuration. No fields, screens, workflows, permission schemes or project settings. Mermix does not ask for that access.
- Create or delete work items, add comments, or log time.
- Touch other Atlassian products, such as Confluence.
The start date
Mermix uses the Start date field built into Jira, the same one the Jira calendar and timeline use, so the dates you push show up there too. If your site has no Start date field, Mermix does not create one. A Jira administrator can restore it from the trash or show it on your projects.
What Mermix keeps
What Mermix stores, for how long, and who it shares it with is in our privacy policy.