Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to disable "Original Estimate" (Time Tracking) requirement for users?

Alexander S. April 12, 2019

Hi,

We use JIRA (server) for end-users group to log requests and for internal development.

We want the users to only provide us with a summary, description and attachments, whereas developers should also be able to log time spent on resolving those issues.

Turning on Time Tracking enabled this feature also for the end users, which we obviously don't want.

Removing time tracking fields from issue creation screen and assigning "work on issue" permissions only to the group of developers didn't help. End users are still unable to log their requests without entering Original Estimate values.

Please advise how to fix this!

1 answer

0 votes
Dave Theodore [Coyote Creek Consulting]
Community Champion
April 12, 2019

Check the managing project permissions docs. The "work on issues" permission grants the ability to move things through the workflow. It has nothing to do with estimation or logging work.  

The "Time Tracking Permissions" section has the permissions you need to use to do what you want.  It's a bit confusing, since the terms used in various places are not consistent, unfortunately.

Alexander S. April 17, 2019

Hi @Dave Theodore [Coyote Creek Consulting],

Unfortunately, this doesn't address the issue - I have "work on issues" permission clearly assigned to the developers, however, request form still asks end users to provide original estimate value in the form.

It appears that the problem stems from the fact that both projects - end user request one and internal development project use the same "Task" issue type. And turning on time tracking in JIRA enables time tracking for all of the projects at once (speak about bad design!) and there's no way to only turn it on for one project and not another.

So the only fix I can think of is create a separate "Task" issue type for one of the projects. I'm reluctant to put this in place, though, as I don't know what implications such change will bring about on existing workflows and old issues with shared "Tasks".

Any other advice you can spare, please, in the light of above?

Thanks!

Suggest an answer

Log in or Sign up to answer