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.

I could imagine, that you can have automatic checklists assigned based on an issue transition. Then multiple checklists would make sense.

Example: Sales call (first discovery call / second technical analysis / third offer creation)

I've voted for this feature because

Example:

Our sales department has as a job, for example, a module after-sale. There are tasks that are always the same and others that depend on the module.

Here it seems to me much more practical to create a checklist for the standard tasks and further checklists for each module.

Of course, I can integrate the standard tasks into every module checklist.

But beware if something changes in the standard tasks. Then I have to change not only the one standard checklist but ALL module checklists!

After conducting an in-depth examination, we have yet to identify significant use cases that would enrich our product. Consequently, we have decided to postpone further development until we receive more feedback from our community. If you're interested in contributing to this process, we would greatly appreciate your input. Please detail how you envision utilizing this feature and explain why this issue has garnered your vote.

+1

For us, this functionality would also be very important.