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

How do I prevent a user from logging time against a task with a Closed or Archived account?

Erin Hickman

We currently use the 'Account' field in Tempo to create our client invoices at the end of the month. We use the reporting feature to create an account report, and add up all the hours logged against that account. Unfortunately, our employees, when creating their tasks sometimes pick the wrong account. For example, the pick 'March 2017' instead of 'March 2018' by mistake. Problem is, it seems users are allowed to log time against tasks with accounts which have been set to both 'Closed' and 'Archived'. Please can you tell us what the purpose of these status are? What is the difference? Is there any way to stop this from happening? Equally, can we prevent a user from picking a task where the task has previously been closed? Thanks!

Accepted answers

All comments

Adrián Plaza [DEISER]

HI @Erin Hickman,

Welcome to Atlassian Community

You can use Status Properties to block edit issues in this status, you can find more information here: https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html

In your case, you need to user jira.issue.editable with value false.

Cheers,

Adrián.

Erin Hickman

Thanks, Adrián. Would this mean that nothing on the tasks with the closed or archive account would be editable? For example, could we add a comment later for reference or would this not be allowed?

Christopher Jaksch

Hi @Erin Hickman,

as far as I understand the Tempo documentation, closed & archived tempo accounts shouldn't be able to be picked as account on issue creation. Therefore no work can be logged on these accounts.

https://tempoplugin.jira.com/wiki/spaces/ACCOUNTS/pages/172163083/Account+Status

Can you please check this once more?

You also should try @Adrián Plaza [DEISER] resolution to block worklog on "closed" issues as tempo does not disable worklog on closed issues by default.

Another thought on that: do your JIRA users log work with the JIRA internal work log?
https://community.atlassian.com/t5/Questions/Log-work-on-closed-Tempo-account-though-Jira-is-allowed/qaq-p/77369

Best wishes
Chris (STAGIL)

Erin Hickman

Hey Chris,

Yes, it prevents them from creating a new task with a closed/archive account, but it doesn't stop them from logging time against an existing task with a closed/archived account. When searching for the task, they can easily pick a similar task that is old/closed. It seems like there should be a validation when logging time against a task with a closed/archived account which says 'You are logging time against a task with an account which is not currently open. Are you sure you want to log time on this task?' Will look into Adrian's suggestion, just want to understand any possible ramifications as this would be a company wide change.

Thanks,

Erin

Christopher Jaksch

Hi @Erin Hickman,

you can disable the worklog on closed/archived accounts in the Tempo global configuration.

Please refer to the Tempo documentation: https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/206274689/Permissions+to+edit+worklogs

As a JIRA administrator, select the check box for the following setting on the Tempo Global configuration page: Users can log work for closed and archived accounts

Hope that helps.

Best wishes
Chris (STAGIL)

Erin Hickman

Great, thanks!!

Welcome!

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

Quick Links

Find more posts tagged with

jira

tempo

account