# Turn several ideas into Jira issues

Review several map ideas together, create their Jira issues in one batch, and see which ideas succeeded or failed.

## Before you start

You need:

- Permission to create issues in every destination Jira project you select.
- A mind map that you can edit.
- At least one ordinary idea that is not already connected to Jira and is not a web-link card.

You can create up to 50 Jira issues in one batch.

Bulk creation is best for issue types that use the fields shown in the dialog. If Jira requires additional fields, create those issues individually or use Jira's full create form.

## Open the batch

1. Select **Bulk Jira** in the map header.
2. Wait for **Bulk create Jira items** to load.

The dialog lists ordinary ideas that can still become Jira issues. Ideas already showing a Jira key and web-link cards are not included.

## Choose which ideas to create

1. Use the checkboxes to select or clear individual rows.
2. Use **Select all nodes** or **Deselect all nodes** when needed.
3. Enter text in **Filter nodes or summaries…** to search summaries, descriptions, hierarchy paths, and project keys.
4. Select **Selected only** to review only the rows that will be created.

The dialog selects no more than 50 rows. If the map contains more eligible ideas, finish one batch and return for the remaining ideas.

## Set shared values

The controls at the top apply to every currently selected, uncreated row.

1. Choose a project to use **Set project for all selected**.
2. Choose an issue type to use **Set issue type for all selected**.
3. Choose a priority to use **Set priority for all selected**, or leave **Use project default** selected.

Changing a shared value does not affect rows that are not selected or rows already created.

## Review each issue

For every selected row, review:

- **Node / Context** — where the idea sits in the map.
- **Project** — where Jira will create the issue.
- **Issue type** — the Jira issue type to create.
- **Summary** — initially copied from the idea text.
- **Description** — initially copied from the idea details, when present.
- **Priority** — a Jira priority or the project default.

You can change these values for one row without changing the others.

The hierarchy path is context for your review. It does not, by itself, create a Jira parent relationship.

## Review proposed parents

A row can show a proposed **Parent issue** when its immediate map parent already has a Jira key.

- Leave the parent connected to send it to Jira.
- Select **Unlink parent** to create the issue without that proposed parent.
- Select **Link parent** to restore a compatible parent that you previously removed.
- Review the **Without inferred parent** count before creating.

If the issue type, parent type, or destination project is incompatible, the row is detached from the proposed parent. A Sub-task still requires a compatible parent and cannot be submitted without one.

See [Create parent and child Jira issues](./parent-and-child-issues.md) before creating a hierarchy for the first time.

## Create the Jira issues

1. Confirm that every selected row has the intended project, issue type, summary, priority, and parent.
2. Select **Create _number_ Jira issues**.
3. Keep the dialog open while the request is running.

The progress area and row badges show **Pending**, **Creating...**, **Created**, or **Failed**. Editing controls remain unavailable while Jira is processing the batch.

## Review the result

For each confirmed success:

- Jira contains a new issue.
- The row shows the confirmed issue key.
- The matching idea becomes a Jira-linked map card.

If every issue succeeds, Mind Map Studio shows a success message and finishes the batch. If the dialog remains visible, select **Done** or **Close**.

## Handle a partial result

If some rows succeed and others fail, Mind Map Studio shows **Created _successful_ of _total_ Jira issues.**

- Successful rows keep their Jira keys and cannot be submitted again in that dialog.
- Successful map ideas become Jira-linked cards.
- Failed rows remain ordinary ideas and can be reviewed again.

Correct a known validation, project, issue-type, priority, or parent problem before submitting the failed rows again.

If the message says Jira did not confirm the result, do not immediately repeat the batch. Check the destination projects for the proposed summaries first; an uncertain request may already have created some issues.

## Good to know

- One batch can contain issues for different projects, but each row must use an issue type and fields accepted by its destination project.
- The dialog does not create a parent row first and then use its new key for another row in the same batch. Create Jira parents before opening the batch when you need hierarchy.
- Only confirmed successes are connected to map ideas.
- Map progress, themes, idea styling, map relationships, and sibling order are not sent to Jira.

## Fix a problem

### No eligible ideas are shown

Every idea may already be connected to Jira or may be a web-link card. Return to the map and add an ordinary idea.

### Create is unavailable

Select at least one row and give every selected row a visible summary. A Sub-task also needs a compatible parent.

### Jira requires fields that are not shown

Cancel the batch and create the affected issue individually. Use **Open Jira create dialog** if Mind Map Studio cannot collect the required fields.

### Some rows failed

Review the failed rows and the destination project. Keep the confirmed Jira keys from successful rows. See [Fix Jira issue problems](./troubleshooting.md) before retrying an uncertain result.

## Related guides

- [Turn an idea into a Jira issue](./create-an-issue.md)
- [Create parent and child Jira issues](./parent-and-child-issues.md)
- [Know what changes in Jira](./what-changes-in-jira.md)