Is it possible to block users from logging time on Epics and Parent tickets? I just want them to log on the subtasks.
the time logging, also the one done with Tempo, is based on the Jira default logging functionality. Users to log the time on an issue need the "Work On Issue" permission configured at the project level and applied to all the issues in the project.
I cannot test it right now but this should work:
If you have separate workflows for Epic, Task, and Subtasks you can update the workflows of the Epics and Tasks by adding to each Status in those workflows the property:
jira.permission.work.denied =
(the value is empty)
In this way, the users will not be able to log time when on those statuses, but since you added the property to all statuses in the workflow, they will not be able to log work on all the issues that are using that workflow.
I hope this helps
Haven't done a lot with tempo time tracking for a while but I'd suggest not making the time fields available on screens related to issue types that you don't intend time to be logged against.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Derek F_ I've included the time fields on a transition and it only seems to allow setting the estimate fields and not the actual logging of time. Granted I haven't got further than that so haven't checked if I've included the incorrect fields. Just reverted to not including them so that people log directly on the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Clare:
In our env, we are not using Tempo. So by default (out of the box with Jira Software Application), log time functionality is enabled by default for any issue type. So typically, one will achieve what you wanted either through business process training of your users or what @Giovanni Melai suggested to control it via the WF customization.
Again, in our env - we have a solid business process training process to our end users on dos and don'ts when they use the application. Maybe, in the future we will look into Tempo for another time reporting solution.
Hope this also helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, if you are open to trying a different app, you might want to check out our Timesheet Builder. It lets you configure very easily who is allowed to work on what, for example subtasks only:
Other notable features include:
Feel free to request a demo here or access our sandbox here.
Thanks! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.