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

Time Tracking - Disabling Ability to log Work for custom issue types

Holger Endres

Hi,

we're using Jira 4.3 with Greenhopper 5.6.5.

Is it possible to disable the ability to log work on issue type base? i.e. It should be possible to log work for, lets say for the issue types "User Story", "Task", "Error" but not for the issue type "epic".

Important: Is it possible only with the build-in time-tracking of Jira? (without any of the existing commercial plugins like tempo etc.)

I tried to remove timetracking field from screen, but still everybody who's allowed to log work can log work.

Thx

Holger

Accepted answers

All comments

Nic Brough -Adaptavist-

Not really. Permissions are done at a project level, not issue type, so the "can log work" permissions follow that and can't be done on a per-issue bases.

You could try to use javascript to remove the work-log from the screens on the issue types you don't want it, but I suspect the users would still be able to get to it via different routes.

Paul Alexander

Old question, but an easy solution exists for this. Assuming you have an existing Workflow for just the Epic issue type, simply add this Property Key to each of the transitions in that Workflow. Leave the Property Value empty. Be sure to publish the workflow after creating the draft.

jira.permission.work.denied

robertno

Thanks for the info. Paul - I found that adding the jira.permission.work.denied to each workflow Step Name (id) --> Properties, was the solution here, rather than the workflow transition (within the On-Demand version).

Maybe this has changed since the solution above was provided as some time ago. Thanks for pointing in right direction however

Nic Brough -Adaptavist-

It's not changed since it was introduced. When I answered, you couldn't do it (reliably). When it was added, it always got added to the Step, not the transition.

Neil McGuirk

I've been trying to find out how to do this for ages.

Finally I can prevent developers logging time where they shouldn't.

Thanks so much

Deniz Oğuz - The Starware

For people looking for a more general solution, you can achieve this by using "Worklog Verification" script feature of WorklogPRO. There are sample scripts in our repository but If you need a custom script, please let me know, we can write it together.

shivamdu

Does jira.permission.work.denied property solution still work? we are on Server

Thomas Rohrer

I can tell that NO.

Nic Brough -Adaptavist-

Eh? It's still working here on 7.13

Thomas Rohrer

My bad :-/ It is works.

Dima Rastaturin

I am on the Cloud, and it's not working at all for us. Seems like Atlassian is not paying any attention to this.

Edward Koh

we are in cloud and i just added the jira.permission.work.denied to every status in our issue-type-specific workflow. seems to hide the "Log Work" option in the UI as we wanted. great solution!