Prevent logging time against closed issue WITHOUT setting issue to be uneditable

[Esther Strom]

We have a new mandate from our finance department to prevent users from logging time against closed issues. I've searched, but every solution I've found seems to rely on workflow properties, specifically jira.issue.editable and jira.permission.work.

I have no problem using properties, but apparently jira.permission.work only works if jira.issue.editable is also in play and set to false. We don't want to make our issues uneditable when they're closed; there are valid cases for a closed issue needing to be edited. We just want to prevent users from logging time against a closed issue.

Does anyone have a solution that will allow us to restrict time logging without rendering an issue uneditable?

We are on Cloud, and we use Tempo Timesheets.

[Mohamed Benziane · Accepted solution]

Hi @Esther Strom 

Did you try jira.permission.work.denied ?

https://confluence.atlassian.com/jirakb/how-to-restrict-log-work-on-a-specific-status-834225982.html

You can also try this

https://community.atlassian.com/t5/Jira-questions/Restrict-work-logging-on-done-issues/qaq-p/843870

Edit:

It seems that there is a trouble with this propertie and Timesheet

[Esther Strom]

Thank you, jira.permission.work.denied does work. I hadn't seen that one mentioned in any of the search results I found.

[Ben America]

hi all,

this is weird for me. 

So i tried to set the property of jira.permission.work.denied = denied in the status property of 'resolved' and 'closed' and it work only for 'closed' ticket. 

We have status of resolve (where issue is resolved) and closed (issue with status resolved will go to closed automatically within 7days if there is no reply from customer). 

When i set the property of jira.permission.work.denied = denied for both 'resolved' and 'closed' it will only prevent me to log time in 'closed' status