What Markdown creates an unchecked Jira checkbox?

Try `- [ ] Task text` in a Jira editor that supports Markdown-style task lists. Confirm the result in your project before relying on it.

How do I mark a Jira Markdown task complete?

Use `- [x] Task text` in supported input, or select the task control in the Jira editor after the list renders.

Why does Jira show the brackets instead of a checkbox?

That field or editor may not parse Markdown task syntax. Use its task-list control or check the project's current editor behavior.

Should I use checkboxes or subtasks?

Use checkboxes for a short checklist. Use subtasks when each item needs its own assignee, status, estimate, or reporting history.

Create Checkboxes in Jira Markdown

In Jira Cloud, create a task list with Markdown-style syntax such as `- [ ] Verify the deployment` and `- [x] Run the smoke test`, when the current editor accepts Markdown task-list input. Jira may convert the syntax into interactive tasks after you press Enter or save the description. Editor behavior can vary by Jira product, field, and rollout state, so test the syntax in a non-production issue first. If Jira leaves the brackets as text, use the editor's task-list control or insert a checklist through the available formatting menu. A converter can generate the source syntax, but it cannot change editor capabilities or permissions.

Use unchecked and checked task syntax

A Markdown task list uses a list marker followed by a bracket pair. Write `- [ ]` for an incomplete item and `- [x]` for a completed item. Keep one task per line and place the task text after the closing bracket. For example, `- [ ] Confirm the rollback plan` creates an unchecked task in editors that support this syntax. Capital `X` is commonly recognized by Markdown processors, but use lowercase `x` for consistent source output. Do not add spaces inside the brackets. Nested tasks need indentation, and their behavior may depend on the Jira editor. Keep task wording action-based so readers can understand the expected result without opening another document.

Check which Jira editor receives the content

Jira has more than one text-editing experience across products and projects. A field may accept rich text, Markdown shortcuts, pasted content, or plain text. The same source can therefore render differently in two issue types or workspaces. Enter a short test in a disposable issue or a private project. If Jira recognizes the syntax, it should display a task control or formatted task list after input is processed. If it displays literal brackets, select the task-list option in the editor instead. Do not repeatedly paste converted content into a live incident or customer issue because repeated conversions can create duplicate markers and confusing history.

Keep task state and issue history clear

A checkbox is useful only when its state has a clear owner and meaning. Use one task for one verifiable action. Put dates, links, and evidence in the task text only when they help the assignee complete the work. For a long checklist, consider subtasks when each item needs its own status, assignee, or reportable estimate. Editing a description task list may not provide the same workflow history as changing an issue status or subtask. Confirm how your Jira project records edits before using checkboxes for audit evidence. A Markdown-to-Jira tool can prepare consistent syntax, but review the rendered result and preserve any existing description content.

How do you do it step by step?

1Open a test Jira issue and confirm that the description editor supports rich text or Markdown-style task lists.
2Write one item per line using `- [ ]` for open tasks and `- [x]` for completed tasks.
3Paste or enter the list, then wait for Jira to transform the syntax or use the editor's task-list control.
4Review indentation, links, completed states, and duplicate items before saving the issue.
5Use subtasks instead when an item requires separate ownership, workflow status, or reporting.

Working example

This input describes a small release checklist with one completed item.

Input

- [x] Build the release package\n- [ ] Verify the checksum\n- [ ] Notify support

Result

Release checklist\n☑ Build the release package\n☐ Verify the checksum\n☐ Notify support

The output illustrates the intended states. Jira may display interactive task controls instead of these Unicode symbols.

Frequently asked questions

What Markdown creates an unchecked Jira checkbox?: Try `- [ ] Task text` in a Jira editor that supports Markdown-style task lists. Confirm the result in your project before relying on it.
How do I mark a Jira Markdown task complete?: Use `- [x] Task text` in supported input, or select the task control in the Jira editor after the list renders.
Why does Jira show the brackets instead of a checkbox?: That field or editor may not parse Markdown task syntax. Use its task-list control or check the project's current editor behavior.
Should I use checkboxes or subtasks?: Use checkboxes for a short checklist. Use subtasks when each item needs its own assignee, status, estimate, or reporting history.