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

BLOCK STATUS ON GENERALL WORKFLOW

Mateusz Janus_emo9ao

Hello Brothers and Sisters,

I have very simple case but I have already lost hope xD

My workflow contains generall statuses (<--ALL).

I want to freeze last statuses DONE and WON;T DO.

So once ticket status changed to DONE user should not be able to "reopen" its.

Any ideas...

Accepted answers

Duc Thang TRAN_1ioe46

Hello @Mateusz Janus

If the idea is to prevent transitions once a ticket reaches "Done" or "Won't Do", here is a solution:

1 - You should remove the "All" transition and use only common transitions for each status , a transition to "Close" from somes statuses except "Cancel" For exem

2025-12-17 14_02_40-.png

2 - Alternatively, as suggested by @Staffan Redelius , once a ticket reaches "Done" or "Won't Do", it can also prevent all modifications, including status changes

All comments

Staffan Redelius

Hi @Mateusz Janus and welcome!

This can be done by setting the workflow properties from Any -> Done and Any -> Closed

Add the property jira.issue.editable = false

Let me know if this helps!

Best regards,
/Staffan

Mateusz Janus_emo9ao

hey @Staffan Redelius thanks for quick response,

you mean THIS properties?

like this.jpg

Staffan Redelius

Hi,

Yes, that is the one!

Please mark my answer as accepted if this helps you. It will make it easier for future visitors to get help.

Best regards,
/Staffan

Duc Thang TRAN_1ioe46

Hello @Mateusz Janus

If the idea is to prevent transitions once a ticket reaches "Done" or "Won't Do", here is a solution:

1 - You should remove the "All" transition and use only common transitions for each status , a transition to "Close" from somes statuses except "Cancel" For exem

2025-12-17 14_02_40-.png

2 - Alternatively, as suggested by @Staffan Redelius , once a ticket reaches "Done" or "Won't Do", it can also prevent all modifications, including status changes

Mateusz Janus_emo9ao

@Staffan Redelius i made this propperty but it does not freeze DONE status. I can still change from DONE to any

Marc Koppelaar

Hi @Mateusz Janus

To relate to @Staffan Redelius solution.

The values are not set correctly on your end, you can't make up a key, this needs to be an official option.

property key: jira.issue.editable

propert value: false

Mateusz Janus_emo9ao

this solution

https://support.atlassian.com/jira/kb/disabling-edits-in-closed-issues-for-jira-tickets/

is for jira CLOUD only

Mateusz Janus_emo9ao

yeah i noticed i made mistake after article but anyway this solution works only for CLOUD. In DC i cannot set up such "freeze" mechanizm

Marc Koppelaar

Hi @Mateusz Janus

The same logic applies for DC, just the link I provided is to a Cloud KB.

Here is the DC link, https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html

Stephen_Lugton

@Mateusz Janus

If you are able to edit the workflow, or ask an admin to edit if for you, a simple way of solving your issue is to add 2 rules to each of the ALL transitions that you don't want to be usable after the work item status is changed to Done or Won't Do:

The second rule would use Won't Do rather than Done in the rule check

Welcome!

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

Quick Links

Find more posts tagged with

jira

transition

jira-data-center

status

data-center