Hi all,

We are currently working on this - Not too far from the finish line. An announcement will come in the change log to update everyone in the coming weeks.

I'm excited to see this highly requested functionality go live and be used!

Cheers,

Dominic

I have created this follow up element here: https://vote.seibert-media.net/checklists-for-atlassian/p/multiple-checklists-per-issue-in-jira-at-the-same-time

Since we discussed this topic some days ago, I thought it would be helpful to gather some more feedback on our ideas. So i quickly sketched out a few concepts. Which version do you prefer / meets your needs the most?

This is a make and break deal if we were to use didit checklist. In our workflows we need multiple checklist to be attached to that ticket.

We have a case where we want different checklists for different stages of the task.

We start with a requirement, and I want some things done.

Then, we add the checkilist for the next stage. This is ideally done by automation so I can decide what checklist to use based on the Jira ticket information.

This also relates to the ability of using the checklists to validate if all the mandatory tasks are done before the task can be progressed to the next stage.

I agree with Dietmar Schuck. I can see having a general "always do" kind of checklist with other small pieces covering smaller custom lists.

Think general setup of a main platform, and then smaller lists for individual modules that have been purchased. Modules may vary between customers.

After talking to the technical team we'd rather plan a situation where you can amend checklists and not have multiple ones in one Jira issue.