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

Prevent users from logging time under Epic?

Tudor Hofnar

Currently a user can log work under an Epic, Issue and Sub-Task. Is there any way to prevent (disable) them from logging work under the Epic while allowing them to log work under the Issue and Sub-Task?

Thanks!

Tudor

Accepted answers

All comments

Rahul Aich [Nagra]

What you can do is define a issue type screen scheme, and for the issue type Epic you remove the field - time tracking from its corresponding screens, so users will not find the field - Original estimate or Time spent field in the first place when they view the Epic.

However you include them for the other issue types.

Here's the link on how it is to be done

https://confluence.atlassian.com/display/AOD/Associating+Screen+and+Issue+Operation+Mappings+with+an+Issue+Type

Hope this helps.

Rahul

Tudor Hofnar

Thanks Rahul, I have already done that so the Time Tracking fields do not appear on Epics. However, if a user navigates to the Epic in JIRA, they can use the 'More Actions' field and Log Work that way....is there any way to disable this option?

I guess the same question was asked here (https://answers.atlassian.com/questions/78960/time-tracking-disabling-ability-to-log-work-for-custom-issue-types) and the answer is no, has there been any change to this?

Jobin Kuruvilla [Adaptavist]

There is a slightly difficult workaround possible. You can have a different workflow for Epics and remove the "Log Work" permission by restricting it on the different statuses in the workflow.

See http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html

Paul Alexander

Tudor - This is very easily solved. 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

Sarah Wilkerson

Thank you! This worked for me

Eitan Mizrahi

How can I define a workflow just for an epic (JIRA software on clound)?

Can you give me an example, please.

Thanks.

Junio Fernandes

Thank you! That worked for me.

Tony Ditola_yvublx

I just did this today, thank you. But a point of clarification: it only works if the property is added to the STATUSES, not the TRANSITIONS. Otherwise, it works great.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

epic

worklog