How can I make sure it is no longer possible to log work on a closed issue in Tempo timesheet?

When I close an issue in JIRA Core I can stil log work through Tempo Timesheets. 

I've added an value on the properties of the workflow so the Log-work button is no longer visible in the Issuescreen, that works but I can still log hours through the Tempo-timesheet function. What am I doing wrong?

In the settings i've checked the function below:

With Regards, Arnaud

1 answer

You could set permission to log for issue assignee and clear assignee when issue is closed. This will prevent logging on closed issues.

Hi Vasilly,

Thanks for your quick answer. Can you tell me where I can arrange that setting?

Although we have multiple users who log work on the same issue, so your suggestion will not work totally, but maybe I can add an other condition. But then I need to know where I can do that. 
 

Maybe you could help setting "Allow logging for uneditable issues" (admin panel/Tempo/General configuration)

Hi Vasiliy.

You can add a JIRA property in your closed status of your workflow that makes the Issue not editable when it's closed - The property is "jira.issue.editable" - See JIRA documentation here: https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html

When using this, you need to make sure that the Tempo Configuration setting mentioned above is not checked. That is, do not allow logging work for uneditable issues.

I´m pretty sure this should solve your issue.

Regards,

Sandra

Hello,

Can you let me know if this is essentially a work around or the intended design to obtain this functionality? I am thinking there would be some attribute that can be changed to simply prohibit someone from logging time against a closed issue. Honestly, I would think this would be the default setting already. Any thoughts?

Hi

We don't look at this as a workaround. This is they way it's configured in JIRA. This is also the way it's done when only using JIRA worklog function, and it's there by default in the JIRA system read-only workflow.

Regards,
Sandra

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

973 views 5 18
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot