How to Add Checkboxes in Jira: A Step-by-Step Setup Guide
Need a clearer way to track choices and tasks? Learn how to add checkboxes in Jira with the right field or issue checklist. Read now to set them up.
Checkboxes in Jira can mean two different things: a selectable field with preset options, or a tick-off task list inside an issue description. Choosing the wrong type can leave your team with a field that does not track the work it needs to finish.
That small mismatch quickly creates friction. Teammates may add checklist items in comments, overlook required steps, or struggle to report on completed choices. It becomes harder to see what is done and what still needs attention.
But here's the truth: you can set up either option with Jira’s built-in features. I’ll walk you through creating a checkbox field, adding a task checklist, placing each where your team can use it, and checking that the setup works.
How to Add Checkboxes in Jira
First, decide what you need to track. Use a checkbox field when people choose one or more predefined options, such as “Needs review” or “Customer notified.” Use a task list when people need to tick off separate actions with their own wording.
- Choose the right project type and issue. Open a sample issue and check whether your project is company-managed or team-managed. The setup menus differ, so this helps you follow the right path.
- Open the custom field settings. For a company-managed Jira Cloud project, go to Jira administration, then find Work items or Issues and select Custom fields. Menu names can vary with Jira’s interface.
- Create a checkbox field. Select the option to create a custom field, choose the Checkboxes field type, and give it a clear name. For example, “Release checks” tells people more than “Checkbox field.”
- Add the selectable options. Enter a separate option for each choice, such as “Security review,” “Help page updated,” and “Support team notified.” Keep options distinct so teammates know exactly what each selection means.
- Make the field available on issues. Add the field to the relevant screens or issue layouts. Check its project and issue-type context too. If the field is missing from a bug but visible on a story, its context or layout may need adjustment.
- Test the field on an issue. Open an issue of the right type, select one or more options, save, then reopen it. Confirm that your selections remain visible and that the field appears where teammates expect it.
For a team-managed project, open the project’s settings, choose an issue type, and use its field controls to add a checkbox field if that option is available. If you need individually worded actions rather than fixed choices, add a task list to the issue description instead.

Choose Between a Checkbox Field and a Task List
These two options look similar, but they serve different jobs. A checkbox field presents a fixed set of choices. A task list lets you write and complete individual actions as work progresses.
For example, a release issue might use a checkbox field for “Security reviewed,” “Customer notice approved,” and “Support briefed.” Each option is a consistent status choice for that issue.
A task list suits a changing sequence of work: “Confirm the release window,” “Ask Maya to test the upgrade,” and “Post the final notice.” A teammate can mark each action complete without asking an administrator to add another field option.
Here's why the distinction matters: a field works well when you want people to select standard values, while a task list is more flexible for day-to-day execution. Pick the one that matches how your team will use and review the information.
Add a Task Checklist to an Issue Description
Open an issue and edit its description. In Jira’s rich-text editor, use the task-list or checklist control in the formatting toolbar. In some Jira interfaces, typing a slash opens a menu of formatting options; choose the task-list option if it appears.
Add one action per line, then save the issue. For example, a new employee setup issue could include “Create account,” “Assign laptop,” and “Schedule orientation.” Teammates can mark each item complete as they go.
Let me explain: this checklist is part of the description, not a custom field with predefined choices. It is useful for visible actions, but it may not behave like a separate field in filters, reports, or automation.
If you cannot find the task-list control, check whether you are editing the description in Jira’s rich-text editor. An administrator may also have configured a different editing experience. As a fallback, use a checkbox custom field for fixed choices or another project-approved checklist approach.
Make the Checkbox Easy to Find and Use
A checkbox is only helpful if teammates can see it at the right point in their workflow. Place a custom field on the issue layout where people create or update that issue type, rather than leaving it buried among rarely used fields.
For example, put “Security review” near the release details on a change issue. A checklist for installation steps belongs in the issue description, where the people doing the work can follow it.
Use plain-language labels and avoid overlapping options. If “Approved” and “Reviewed” mean different things, explain that difference. Otherwise, people may select both without knowing which one signals that work is ready to proceed.
Try the setup with a few teammates before rolling it out widely. Ask them to create an issue, update the checkbox, and find the status again. Their experience can reveal confusing labels or placement that an administrator might miss.
Check Visibility, Permissions, and Reporting
If someone cannot see a field, check its project and issue-type context, screen configuration, and issue layout. A field can exist in Jira while remaining unavailable on the specific issue your teammate opened.
Permissions can also affect who may edit an issue. Compare what an administrator sees with what a regular project teammate sees. If only the administrator can make changes, review the project’s permissions and the field’s configuration.
Custom checkbox fields can be useful in Jira search, filters, and reports, depending on the field and configuration. Task lists in descriptions are better suited to tracking visible actions than summarizing status across many issues.
For example, if a release manager needs to find every issue where “Security review” is unchecked, a custom field is usually a better fit. If a developer needs to tick off three changing implementation tasks, a description checklist is more practical.
ONES.com Solution for Coordinating Project Work
ONES.com brings project management and knowledge management together in one platform. ONES Project is a Jira alternative for managing work, while ONES Wiki provides a knowledge base as a Confluence alternative. They are sold separately, so you can choose the capabilities that fit your team.

The value is practical: when checkbox-related work connects to project workflows, clear fields and shared guidance can help reduce confusion. The following capabilities address common coordination needs:
- Pain: Teams need consistent ways to track status. ONES capability: Custom workflows and fields let you shape work item details. Result: Teammates can record the choices your process requires.
- Pain: Sprint tasks and project issues are difficult to coordinate. ONES capability: Sprint management supports planning and tracking work. Result: Teams can see how individual tasks fit into a sprint.
- Pain: Repetitive updates take time. ONES capability: Automation can handle configured workflow actions. Result: Your team can spend less time repeating routine steps.
- Pain: Project leads need visibility into progress. ONES capability: Built-in reporting summarizes project activity. Result: Teams can review progress without relying only on manual status checks.
- Pain: Teams want to keep familiar issue processes. ONES capability: Jira-compatible workflows support established project patterns. Result: Teams can retain recognizable ways of organizing work.
- Pain: A growing plugin set can add maintenance overhead. ONES capability: Native project features include workflows, fields, sprint management, and reporting. Result: Teams may be able to meet more needs without adding as many plugins.
- Pain: Some organizations need control over where the platform runs. ONES capability: Deployment options include Cloud, On-Premise, Private Cloud, and Air-gapped environments. Result: Teams can select an environment that fits their operational requirements.
- Pain: Teams need to document how a workflow works. ONES capability: ONES Wiki offers a knowledge base, sold separately from ONES Project. Result: Teams can maintain guidance alongside their project management setup.
For example, a release team could use ONES Project to manage work items and coordinate sprint tasks. It could keep release instructions in ONES Wiki, giving teammates a place to check the process while updating project work.
ONES.com offers a free plan for up to 30 seats. Cloud and self-hosted versions have full feature parity, giving teams a choice of deployment while retaining access to the same feature set.
Common Checkbox Setup Challenges
- The field does not appear. Check whether it is added to the right screen or issue layout. Also review its project and issue-type context, especially if it appears on one issue type but not another.
- Teammates cannot edit the field. Check their project permissions and issue access. Compare the field’s behavior in a regular teammate’s account with its behavior for an administrator.
- The field offers the wrong kind of selection. A checkbox field is intended for choosing among its configured options. If people need to write and complete changing actions, use a task list instead.
- Checkbox wording causes confusion. Replace vague labels with specific choices. For example, “Ready” may be unclear, while “Support team notified” describes a verifiable action.
- The team expects task lists to appear in reports. Task lists in descriptions may not provide the same reporting behavior as a custom field. Use a field when you need consistent values for searching or reporting.
FAQs About Checkboxes in Jira
Can I add checkboxes to a Jira issue without creating a custom field?
Yes. You can add a task list to an issue description using Jira’s task-list or checklist formatting control, when it is available in your editor. This works well for actions that need separate completion marks. It does not create the same kind of structured field as a custom checkbox field, so choose based on whether you need a flexible task list or fixed selectable options.
What is the difference between a checkbox field and a task list?
A checkbox field lets someone select one or more predefined options, such as “Security review” or “Help page updated.” A task list contains individual actions that can be written and checked off as work progresses. For example, use a field to record standard release checks and a task list to track the specific steps needed to complete one release.
Why can’t I see my custom checkbox field on an issue?
The field may not be included in the issue’s screen or layout, or its context may exclude that project or issue type. Check those settings first. If the field appears for one type of issue but not another, compare their configurations. You should also confirm that your Jira permissions allow you to view and edit the issue.
Can I report on checkbox selections in Jira?
Custom checkbox fields are generally a better fit for searches, filters, and reports than task lists written in descriptions. The exact reporting behavior depends on your Jira configuration and the field. If reporting matters, test a sample issue and confirm that the field’s selected options can be found in the views your team uses.
Can a checkbox field contain options that teammates add themselves?
Checkbox field choices are configured as options for that field; they are not the same as writing a new task in a checklist. If your team needs actions that vary from issue to issue, use a task list in the description. If the team needs new standard choices, ask a Jira administrator to update the field configuration.
Conclusion
To add checkboxes in Jira, first decide whether you need fixed choices or a flexible task list. Create a custom checkbox field for standard selections, or add a task list to an issue description for individual actions.
Then check that the field or checklist appears where teammates work, test it with a regular project member, and confirm the setup supports the reporting you need. That small setup check can prevent confusion later. When project coordination calls for a different approach, ONES.com offers another way to manage workflows, fields, and team knowledge.