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; } } }

Why is it allowing me to close issue when checklist isn't complete?

Michael Arndt_smtys6

I have a fairly simple workflow. I have it setup to confirm that all Checklist Pro items are complete before moving to done. Also subtask issues under conditions. It still allows transferring to DONE even when checklist is incomplete.

Here's my workflow, conditions and validators. Changes have been published.

What am I doing wrong?

Accepted answers

Jack Hunter _HeroCoders_

Hello @Michael Arndt,

Your setup looks good at first sight.

Please double check that:

the workflow is "published" and not only saved as "draft"
the issues you test with "close transition" are in a project that uses the workflow presented on the screenshots
custom fields integration is enabled in Checklist Pro global settings: https://gebsun-support.atlassian.net/wiki/spaces/IC/pages/907542582/Disable+Enable+custom+fields+integration

Let us know if that helps.

Cheers,
Jack

All comments

Jack Hunter _HeroCoders_

Hello @Michael Arndt,

Your setup looks good at first sight.

Please double check that:

the workflow is "published" and not only saved as "draft"
the issues you test with "close transition" are in a project that uses the workflow presented on the screenshots
custom fields integration is enabled in Checklist Pro global settings: https://gebsun-support.atlassian.net/wiki/spaces/IC/pages/907542582/Disable+Enable+custom+fields+integration

Let us know if that helps.

Cheers,
Jack

Michael Arndt_smtys6

Thanks Jack. It was actually setup right. I just wasn't testing it correctly.

I was get an error after selecting a resolution and clicking the DONE button. I'm used to most action rejecting the transition as soon as it's dropped into the Done status.

Jack Hunter _HeroCoders_

Perfect. I'm glad it helped.

The difference between various ways of rejecting transition comes from Atlassian, and we do not control it, unfortunately.

The checklist can only tell Jira "do not allow this transition" with an appropriate message, but it is up to Jira how it presents the information to the user.

I have updated documentation to reflect the current behavior: https://gebsun-support.atlassian.net/wiki/spaces/IC/pages/728039472/Block+workflow+transition+if+checklist+is+not+complete

Cheers,
Jack

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