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...
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
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
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
See also, https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
this solution
https://support.atlassian.com/jira/kb/disabling-edits-in-closed-issues-for-jira-tickets/
is for jira CLOUD only
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Staffan Redelius i made this propperty but it does not freeze DONE status. I can still change from DONE to any
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.