nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can a checklist be required to close a JIRA card

Cindy Franklin

We would like to use the checklist function for all the steps a developer needs to do for work to be complete. We'd like the card to not be closable until the check list is done. Is this possible? I've searched but haven't found anything - if someone can point me in the right direction, would really appreciate it.

Accepted answers

All comments

Mikael Sandberg

Hi @Cindy Franklin,

Welcome to Atlassian Community!

If you are referring to the action items that you can add in the description then the answer is no, you cannot prevent a work item from being closed until they are all checked off. There are apps in the Marketplace, I used Checklist for Jira at my previous job and I believe you can set it up to the checklist has to be complete before you can close the work item, but that needs to be verified.

Viktoriia Golovtseva (TitanApps)

Hey @Cindy Franklin

Welcome to the community!

Jira doesn’t support this natively with its built-in checklists, but as the company's representative I would recommend Smart Checklist for Jira to implement it. It’s possible to require that all checklist items be completed before a Jira issue (card) is moved to “Done” or any other status. You’d typically do this by adding a workflow validator that checks the checklist status during the transition.

In addition the app allows you to define mandatory checklist items, set custom statuses, and block issue transitions until all required items are marked complete. It also supports templates, automation, and runs fully on Atlassian Forge, meaning all data stays within Atlassian infrastructure, which can be a plus if you work in a regulated environment.

unknown

Hello @Cindy Franklin

Jira’s built-in Action Items are quite limited—they don’t support automation or validation, so if your use case involves ensuring tasks are completed before progressing an issue, they may not be enough.

To handle this, you’ll likely need a third-party checklist app from the Atlassian Marketplace. One example is Didit Checklists for Jira, which I represent. It offers more control than the default checkboxes.

For instance, you can configure it so that an issue/ work item can’t be moved to “Done” unless all checklist items are completed. This isn’t possible with native Action Items. You also get additional features like the ability to skip tasks, progress tracking, and audit logs. Hope this helps

Cindy Franklin

Hi @Mikael Sandberg

Thanks for this info! I will pass it on to the folks that would know if we can get the app.

Cindy

Cindy Franklin

Thanks @Viktoriia Golovtseva _TitanApps_

I'll make sure my company is aware of this option.

Cindy

Cindy Franklin

Thanks @[deleted]

I'll pass this on to our group.

Cindy

Tomasz Korusiewicz_SolDevelo

Hi @Cindy Franklin ,

Besides Jira's native Work Items, which lack more advanced functionality, there are no other native checklist-style options. For this reason, as a representative of SolDevelo development team, I can suggest our third-party Atlassian Marketplace app “Multiple Checklists for Jira”.

Per your needs, Multiple Checklists allows you to organize your and your colleagues’ work in a clear and easy-to-understand way with the use of easy trackable lists of tasks.

The app also allows users to add multiple checklists straight into work items (issues), so it is possible to manage a variety of tasks simultaneously from one work item, with the addition of individual and customizable statuses for each item!

After opening the app within the Jira work item, the checklists should always be available from there, including their statuses.

Additionally, if you want to avoid repeating the same procedures and adding the same data while managing your checklists, you can automate them by creating templates that can be then automatically added to specific issue types, or even make use of JQL filters.

If you are interested in this solution, we kindly invite you to check it out!

Regards,
Tomasz

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud