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

criteria for releasing versions.

jeroen.wilmes

We do use Releases in JIRA for releasing versions.

We do NOT use resolutions.

Criteria for Releasing versions is that all issues need to be in status done AND resolution may not be "unresolved".

Is it possible to change the criteria for releasing issues in Jira Cloud?

As we do not use resolutions (status is enough) all issues have the default value "unresolved" and for that reason we cannot release a version, other than " accepting all unresolved issues" which is not a nice way to work.

Accepted answers

John Funk

Hi Jeroen - Welcome to the Atlassian Community!

No, you will not be able to change the criteria. Is there a reason you do not want to populate the Resolution field when completing an issue?

Dave Mathijs

Hi @jeroen_wilmes You may not use Resolutions as criterium for your releases, but the Resolution field is essential for Jira to determine whether an issue is open or resolved (i.e. done)

Why don't your set an automatic resolution (f.e. Done) for status 'Done' via a post function in your workflow?

All comments

John Funk

Hi Jeroen - Welcome to the Atlassian Community!

No, you will not be able to change the criteria. Is there a reason you do not want to populate the Resolution field when completing an issue?

Dave Mathijs

Hi @jeroen_wilmes You may not use Resolutions as criterium for your releases, but the Resolution field is essential for Jira to determine whether an issue is open or resolved (i.e. done)

Why don't your set an automatic resolution (f.e. Done) for status 'Done' via a post function in your workflow?

jeroen.wilmes

Thanks Dave,

I agree on this. I had a closer look on how we organized the workflows and I discovered that we dit not set it up consequently.

Either we should use a screen for giving a resolution value and make that field required via the validator for entering the status.

We should give the set the resolution field to "resolve" by creating the post function entering the status done. (and don't forget to clear that field if we enable issue to be re-opened again.

jeroen.wilmes

Thanks John, see above.

John Funk

You are welcome.

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