Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hello,
I use EPICs for grouping tasks/stories (like a generic integration to a specific customer of mine) and I don't want used them otherwise (for log work). The works are logged on tasks or on stories.
Can I disable "log work" just for EPICs?
Thanks.
Hi Eitan,
You may prevent users from logging time in Epics by following these steps:
After applying this property, users will see an error on trying to log work on an Epic, preventing them from recording worklogs in Epics.
Hope it helps.
Great Ignacio!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Ignacio! This is a real help. Do you know where can I learn more about available properties like this one ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure! There's a good article about workflow properties here:
https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nice one!
One small addition, according to Atlassian, property value should be "denied" . But I noticed that it also works with an empty value.
More information can be found here: https://confluence.atlassian.com/jirakb/how-to-restrict-log-work-on-a-specific-status-834225982.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
should this control be applied to every project manually or you have any global settings?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Eitan,
I think that this cannot be done out of the box.
You can try with an listener, capturing the work logged on issue events and delete them, but this is counterintuitive for the end user and one thing more to maintain and check.
Maybe the best solution is user education and to exclude the epics from the queries / reports you use for time tracking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have heard that workflow may solve that, but I don't know how.
As the link - I didn't understand how to link a workflow to an epic (It just create a new workflow).
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.