Know what changes in Jira
Understand which Mind Map Studio actions create or change Jira data and which actions stay only on the map.
Compare common actions
| What you do | What changes in Jira | What changes on the map |
|---|---|---|
| Add an ordinary idea | Nothing | A new idea is saved on the map. |
| Add an existing Jira issue from Jira backlog | Nothing | A new card is saved with the issue key and a snapshot of its summary and type. |
| Create one Jira issue with the idea attachment selected | Jira creates the issue with the submitted fields. | The selected idea becomes a Jira-linked card after Jira confirms the key. |
| Create one Jira issue without an idea attachment | Jira creates the issue with the submitted fields. | The existing map stays unchanged; the issue is added to the recent-issue list for the session. |
| Create several Jira issues | Jira creates each successful issue. | Each successfully matched idea becomes a Jira-linked card. Failed ideas remain ordinary map ideas. |
| Keep a proposed parent selected during creation | Jira receives that parent key and validates the hierarchy. | The existing map branch stays in place. |
| Change idea progress, styling, or layout | Nothing | The map appearance or progress changes. |
| Add or label a map relationship | Nothing | The label changes the current canvas view and PNG export. It is not retained after reopening the map in the current release. |
| Rename, move, or delete a Jira-linked map card | Nothing | Only the map changes. The Jira issue remains. |
Know which fields are sent during creation
Mind Map Studio can send these values when you create a Jira issue:
- Destination project.
- Issue type.
- Summary.
- Description, when entered and supported by the Jira project.
- Priority, when selected.
- Supported required text or single-choice fields shown in the dialog.
- A compatible parent issue key, when the parent option is selected.
Jira applies its own defaults and validates the request. If the project requires other fields, use Jira's full create form.
Know what stays only on the map
These do not update Jira:
- Idea progress such as To do, In progress, Stalled, or Done.
- Idea colors, icons, themes, and layout.
- Map folders and map visibility.
- Branch placement and sibling order.
- Map relationships and their labels while the map remains open. Relationship-label changes are not retained after reopening the map in the current release.
- Collapsed branches, focus filters, and search state.
Understand a Jira-linked card
A Jira-linked card stores a confirmed Jira key on the map and lets you open that issue in Jira.
It is not a two-way field synchronization:
- Renaming the map card does not rename the Jira issue.
- Changing the map card's progress does not transition the Jira workflow.
- Deleting the map card does not delete the Jira issue.
- Editing the issue in Jira does not automatically rewrite the existing map card.
- Moving the card or changing its map parent does not change the Jira parent.
To work with current issue fields, select the Jira key and continue in Jira.
Jira backlog refreshes only the current project. An issue created in another project can appear there for the current session, but it is not returned by a refreshed current-project list.
Understand parents and relationships
A parent selected in Create Jira issue changes Jira only as part of creating that issue. Jira validates whether the parent and child types are compatible.
The visual branch remains a map structure. Changing it later does not update Jira hierarchy.
A map relationship is always map-only in the current release. Adding a relation label does not create a Jira issue link.
Use Jira's full create form
When you select Open Jira create dialog, any issue you finish there is created by Jira. Mind Map Studio does not automatically receive and attach that issue key.
If the issue belongs to the current project, return to the map and add it from the recent-issue list. For another project, keep the issue key and continue in Jira; the current project's list cannot attach it.
Check before you continue
After a Jira creation action:
- Wait for a confirmed Jira key.
- Select Open issue key ā or the key on the map card.
- Check the project, issue type, fields, and parent in Jira.
If Jira did not confirm the result, check Jira before repeating the action to avoid creating a duplicate.