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


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.



4 answers

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.


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

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.

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

This solution is not working anymore, any other suggestions? 



This is not working any longer for me either.

I am trying to control which Issue Types can log time.

I have build two workflows, one for stories, epics and tasks which deny time tracking using jira.permission.work.denied and one for sub-tasks and bugs which allows time tracking.

The differences in permission on the two work flows have no effect. All issue types are still able tot track time.

However, if I add "All Unassigned Issue Types" to the workflow which disables time tracking, time tracking is removed for ALL issue types.

It appears the mapping of "All Unassigned Issue Types" is overriding the permissions assignment of specific issue types.

I have tried assigning "All Unassigned Issue Types" to its own workflow which allows time tracking whilst leaving specific issues in the "with time tracking" and "without time tracking" workflows but jira.permission.work.denied is still ignored.

If you're on Cloud like me there is an outstanding bug that causes this property to be ignored in certain cases. We're still waiting for a fix. I can't even remember all of the details, but overall, workflows with certain properties (this one included) on them aren't being honored.

I am on cloud. Thanks for the heads up Paul.

Can't tell you how many hours I have spent checking and rechecking my settings to try to get this to work.

I can't begin to tell you how long we've been waiting for a fix to this problem;). I'd have to spend time looking that one up. I probably created that thread somewhere in here. I'm watching the atlassian bug that the note here probably points to.


 Is this issue fixed? I am facing the same issue. 

I just tried this, and while it's a hassle to have to create a whole new workflow, and manually enter the property into each transition - it seems to work. Even if it doesn't work 100%, it's still going to prevent most of the avenues for incorrectly-placed estimates or work logs. 

FWIW i copied the existing workflow, applied it to the appropriate issue types, and added the property to every workflow transition. I still had to remove the field from the the create/edit screens of the issues, but now there doesn't seem to be a way to log time to them. I'm sure Nic Brough would say we're doing it wrong, but it works for us.

0 votes

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.

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. 

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,173 views 5 10
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