Would be useful to have either a method of bypassing the default OLA for tasks through workflows or have the ability to turn off default OLA’s at a workspace level.
Currently any custom OLA enabled in any workspace will turn on the default OLA in the global space, as a result if any custom OLA is active it is impossible to set a due date trough workflows for tasks in any workspace including using the API as it gets over written by the global default OLA.
New Idea
Global Default OLA Bypass for Tasks
Global default OLA bypass settings usually come up when people are trying to streamline task execution and avoid unnecessary interruptions in automated or staged workflows. It’s interesting how similar ideas show up in gaming and app development, where controlled access and temporary permissions are used for testing features before full release. Test environments help reduce risk while still allowing users to explore functionality. I’ve seen this approach discussed in gaming contexts too, including platforms like https://unlockbetaservers.com/, which focus on safe, time limited access for beta testing. The concept of bypassing friction during testing really applies across many systems.
+5Just wanted to chime in and bump this thread because this is a huge issue with the way Task generation is handled at the moment. Tasks that are generated by a ticket generally have contextual due dates that are required for the proper completion of the ticket and OLAs are not context aware enough to provide a good solution to the problem. This wouldn’t really be an issue if the “Due Date” field wasn’t blocked off from being edited, where in its present form it shows a message that says “OLA policy will override the Due Date set manually.”
Join the Community
Already have an account? Login.
Sign in to the Community
No account yet? Create an account.
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.