Plan a Jira release with a mind map

See the current Jira project's unreleased versions, bring their assigned issues onto a map, and coordinate deployment work in a shared release runbook.

#Before you start

You need:

• Permission to view the Jira project and its issues.
• A mind map that you can edit if you want to add release issues to it.
• Jira issues with Fix versions already assigned in Jira if you want them to appear under a release.

The release panel uses the current Jira project. Create versions and assign Fix versions in Jira before using Mind Map Studio to plan around them.

#Open Jira releases

1. Select Jira releases in the map header.
2. Wait for the unreleased Jira versions to load.
3. Find the version you want to plan around.

Each version card shows Attached issues: Jira issues that are already assigned to that version in Jira. It also provides Release Runbook & Notes for planning work that Mind Map Studio stores separately.

The following card shows an unreleased version after a Jira issue has been assigned to it through Jira's Fix versions field.

Unreleased version 3.0.0 showing one sanitized assigned Jira issue.

#Understand an empty release

An unreleased version can be useful before any Jira issues have been assigned to it. In that case, the version shows No Jira issues assigned to this release. You can still add tags and begin its deployment runbook.

These screenshots intentionally show that honest empty state. Nothing failed to load: version 3.0.0 simply has no assigned Jira issues, Mind Map Studio tags, or deployment steps yet.

Unreleased Jira version card showing that version 3.0.0 has no assigned issues.

Empty release runbook with no assigned Jira issues, tags, or deployment steps.

#Add an assigned issue to the map

1. Select the idea that should become the issue's map parent.
2. Find the Jira version under Jira releases.
3. Find the issue under Attached issues.
4. Hover over the issue and select its plus button.

Mind Map Studio adds a child card with the Jira key and summary. You can also drag an issue from the release panel onto the canvas and drop it near the idea that should become its parent.

Adding the card changes the map only. It does not assign or change the issue's Fix versions, edit the issue, or create a Jira issue link.

#Refresh the release list

Select Refresh Jira releases at the top of the panel when a version or issue assignment has changed in Jira.

The refresh requests the current unreleased versions and their assigned issues from Jira Cloud. Opening Release Runbook & Notes loads the saved Mind Map Studio runbook for that project and version. Refreshing does not change anything in Jira.

If an issue still does not appear, open it in Jira and confirm that its Fix versions field contains the expected version in the current project.

#Create a release runbook

1. Find the Jira version under Jira releases.
2. Select Release Runbook & Notes.
3. Enter a deployment step, then press Enter or select the add button.
4. Add the remaining steps in the order the team should complete them.

Use short, action-based steps such as “Confirm production backup,” “Deploy the app,” and “Run the smoke test.” The runbook belongs to this Jira project and release, so other people working with the same release can follow the same sequence.

#Organize and complete the runbook

• Mark a step complete with its checkbox.
• Use Move step up or Move step down to change the deployment order.
• Use Delete step to remove a step that is no longer needed.
• Follow the completed-step count and progress bar to see how much of the runbook is finished.

The progress describes Mind Map Studio runbook steps. It does not change the Jira release status or any Jira issue status.

#Add runbook tags

Use Add tag to create a short marker such as backend, mobile, or approval. You can also type / while writing a deployment step to create or insert a tag.

These are Mind Map Studio tags for organizing the release runbook. They are not Jira labels and are not written to the attached Jira issues.

#Check the result

Your release plan is ready when:

• The expected unreleased Jira version appears in Jira releases.
• Its Attached issues match the issues already assigned to that version in Jira.
• Any issues you added appear as Jira-linked cards on the map.
• The runbook steps are in the intended order.
• The completed-step count changes when you mark a step complete.

#Know what stays in Jira and Mind Map Studio

• Jira releases does not create or edit Jira versions.
• It does not assign, remove, or change an issue's Fix versions.
• It does not show Jira release dates.
• The release runbook is stored by Mind Map Studio. It is not copied into the Jira version description.
• Runbook tags are not Jira labels.
• Adding an attached issue to the map does not edit the Jira issue.

Use Jira when you need to create a version, set its release date, change its release status, edit its description, or assign issues to it. Return to Mind Map Studio and refresh when you are ready to plan visually around those Jira changes.

#Fix a problem

#A version does not appear

The panel shows unreleased versions from the current Jira project. Confirm that you are in the expected project, check that the version is not already released, then select Refresh Jira releases.

#An assigned issue does not appear

Open the issue in Jira and check its Fix versions field. After Jira saves the assignment, return to Mind Map Studio and refresh the release list.

#The add button is unavailable

Select an editable idea on the map first. The selected idea becomes the new card's map parent.

#Related guides

• Add existing Jira issues to a map
• Know what changes in Jira
• Build and edit a mind map