Turn an idea into a Jira issue
Create a Jira issue from a map idea and choose whether the new issue should remain connected to that idea on the map.
Before you start
You need:
- Permission to create issues in the destination Jira project.
- A mind map that you can edit if you want to connect the new issue to an idea.
Jira projects can require different fields. Mind Map Studio shows the supported required fields after you choose a project and issue type.
Start from an idea
- Select the idea that you want to turn into a Jira issue.
- Choose Jira issue from the selected-idea toolbar. You can also select the plus button on the idea, Create Jira issue (J) in the bottom toolbar, or Jira issue in the map header.
- Wait for the Create Jira issue dialog to load.
The idea text is used as the initial Summary. Existing idea details are used as the initial description.
To create an issue without connecting it to an idea, open the dialog without an ordinary idea selected, or turn off the idea attachment in the dialog.
Choose the Jira project and issue type
- Select the project key at the top of the dialog.
- Search for and select the destination project if it is not the current project.
- Select the issue type beside the project key.
The project list contains Jira projects available to your account. The issue types and required fields can change when you select another project.
If a project or issue type is missing, you may not have permission to create that kind of issue there, or the Jira project may not offer it.
Add the issue details
- Review or edit Summary.
- Add a description in Description / notes if needed.
- Select Priority, or leave Use project default selected.
- Complete every field shown under Required Jira fields:.
The reporter is your Jira account. Jira applies the destination project's defaults for fields that are not shown.
Review the proposed parent
If the idea's immediate map parent is already connected to a Jira issue, the dialog shows a parent card.
- Leave Link as child of issue key selected to send that parent to Jira.
- Clear it to create the issue without the proposed parent.
- If the parent and child types are incompatible, Mind Map Studio disables the option and explains that the issue will be created without that parent.
A Sub-task cannot be created without a compatible parent. See Create parent and child Jira issues for the complete workflow.
Choose whether to connect the issue to the idea
When you started from an idea, the dialog shows an attachment control with that idea's name.
- Leave it selected to turn the idea into a Jira-linked map card after Jira confirms creation.
- Clear it to turn the attachment off if you want the issue to remain only in Jira and the recent-issue list.
Connecting the card does not create a Jira issue link. It stores the confirmed Jira key on the map idea.
Create the issue
- Review the project, issue type, summary, required fields, proposed parent, and idea attachment.
- Select Create. You can also press Command+Enter on macOS or Ctrl+Enter on Windows or Linux.
- Wait for Jira to confirm an issue key.
When creation succeeds, Mind Map Studio shows the new key and an Open issue key ā action.
If the idea attachment was selected, the idea becomes a Jira-linked card and keeps its place in the map. If it was not selected, the map idea stays unchanged.
Use Jira's full create form
Select Open in Jira, Open Jira create dialog, or the external-link button labeled Open full native Jira create dialog when:
- The issue type requires a field that Mind Map Studio does not support.
- You need a Jira workflow or field that is not shown.
- Mind Map Studio tells you to use the native Jira form.
Confirm the destination project in Jira before creating the issue. An issue created in Jira's form is not automatically connected to the map. If it belongs to the current project, return to Mind Map Studio 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.
Create another issue
Select Create another before creating if you want the dialog to stay open after Jira confirms the issue.
If the dialog is attached to an idea, remember that one idea displays one Jira key. Turn the idea attachment off before creating another independent issue, or close the dialog and select a different idea.
Check the result
The issue was created successfully when:
- Jira returns an issue key.
- Open issue key ā opens the expected issue in the chosen project.
- A connected idea shows that Jira key on the map.
- The issue is available in its destination Jira project.
Good to know
- Creating an issue can send the project, issue type, summary, description, priority, supported required fields, and an active parent selection to Jira.
- Map styling, map relationships, idea progress, and sibling order are not sent to Jira.
- After creation, changing the map card does not update the Jira issue, and changing the Jira issue does not automatically update the existing map card.
- Jira backlog refreshes only the current project. An issue created in another project may appear there for the current session, but it is not part of the current project's refreshed results.
- If Jira says it did not confirm the result, check the destination project before trying again. The issue may already exist.
Fix a problem
Required fields are missing
Complete every field under Required Jira fields:. If the dialog says the issue type requires fields supported only in Jira, use Open Jira create dialog.
You do not have permission
Choose a project where you can create issues, or ask a Jira administrator for the required project permission.
The issue was created but the idea did not change
The idea attachment may have been off, the map may have become read-only, or its save may have failed after Jira created the issue. If the issue belongs to the current project, keep the Jira key and add it from Jira backlog when the map is editable. For an issue created in another project, keep the key and open it in Jira; the current project's recent-issue list cannot recover that attachment.
For more help, see Fix Jira issue problems.