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

Is there any way to have issues not crossed-off when having any other resolutions set, except "Closed"?

Marius Daniel A

Hello,

I am currently configuring Jira for some projects with custom workflows that include custom statuses and transitions.

We would like to have several custom resolutions like "Open, Postponed, Approved, On Hold etc". If I add any of these resolutions as post functions to transitions, the issue gets the Strike mark, being considered resolved, somehow (I believe this is how Jira actually behaves).

Is there any way to make all the resolutions except "Done" or "Closed" (for example) NOT to strike the ticket as it was resolved when the resolution is changed?

Thank you in advance,

Accepted answers

Nic Brough -Adaptavist-

The resolution and strike out is a simple concept.

If the resolution is set to anything, your issue is resolved. That's the end of it.

What you need to do is only set resolution when you go into a "closed" status. Check the screens you use on all your transitions, and most importantly, the screens you use for "edit" and "create" issue. You MUST NOT have resolution on those screens, as when it's on-screen, it gets set.

All comments

Jobin Kuruvilla [Adaptavist]

Not possible without changing the JIRA source code. The strike through just means that the issue is brought to closure (irrespective of the workflow status).

Having resolutions like Open is not a good idea because it should be handled by the workflow status. Open, Postponed, Approved, On Hold etc should be part of the workflow (i.e. a state in the workflow).

Marius Daniel A

Thank you for your answer.

Nic Brough -Adaptavist-

The resolution and strike out is a simple concept.

If the resolution is set to anything, your issue is resolved. That's the end of it.

Marius Daniel A

This was our solution as well. Thanks

Welcome!

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

Quick Links

Find more posts tagged with

jira