FYI, in case anyone in the future comes here looking for the property to do this with Tempo (like I did):
jira.permission.work.denied ---> value: denied
I tried the answer Philippe suggested and it didn't work in my Cloud instance. Get a crazy error.
I manage this differently. I have set user permissions on "Resolve Issues" to project managers only. Setting this permission restricts others from closing or reopening issues. This manages the time entry issue because a user can only edit Time on an issue if they reopen a closed issue. Restricting the Re-Open to only Project Mangers restricts users abilities to add time after the issue is closed. If you have a process were team members can close issues on their own this solution may not work for you.
I'm using JIRA Cloud too and don't have a solution to this yet. I don't follow Tom's solution - is he saying that restricting who can close an issue will stop work being logged when closed?
We have just two statuses - open and closed. How do I stop work being logged when an issue is closed?
Here is the premise I'm working with. Users can't edit their time against an issue that is closed.
My approach is to restrict who can re-open a closed issue because the issue at hand is "How can I prevent logging work time on a closed JIRA issue?" In order for a user to add more time to a closed issue they need to first re-open an issue and then enter the time. I just restrict the ability to re-open tickets to Project Managers.
This is done by going into your Permisssion Scheme and changing the "Resolve Issues" Project Permission to include only the people you want to be able to "resolve" or "reopen" and issue.
This could be problematic if you have allowed everyone to resolve an issue. Just remember that "resolving" and closing are two different functions. So, I would say, change your Resolve Issue permissions and see if that fixes your issue. It sounds like you are not using "resolve" in your workflow so it is going to be OK.
Thanks for responding so quickly Tom. The problem I am seeing is that the people can log time against an issue *while it's closed*. It is for a custom workflow another admin created with just two states (open and closed) - I think this might be the root of the problem: It doesn't happen on the default workflows I have.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events