Feature Requests

Lock Task Completions
Overview A customer has requested enhanced control over task and project locking to better support read-only collaboration scenarios, particularly when working with external stakeholders (guests). Current Limitation Tasks can be locked, but users (including guests) may still be able to mark tasks as completed. There is currently no way to fully restrict interaction (e.g., completion status) once a task is locked. At the project level, there is no option to enforce a fully read-only mode across all tasks. This creates challenges for teams that want to share visibility without allowing any modifications. Customer Need The customer is looking for a way to ensure that when a task or project is locked, it becomes strictly read-only, meaning: No user (especially guests) can mark tasks as complete No updates or changes can be made to the task Proposed Solutions Option 1: Project-Level Lock (Preferred) Ability to lock an entire project All tasks within the project become fully read-only No edits, updates, or status changes (including completion) allowed Option 2: Enhanced Task Locking When a task is locked, it should also: Disable the ability to mark the task as completed Prevent any further interaction (comments, edits, etc. – depending on scope) Use Case Sharing project progress with external stakeholders or clients Providing visibility without risk of accidental updates Ensuring data integrity and control during review or approval phases Impact / Value Improves governance and control over project data Enables better client-facing use cases Reduces risk of unauthorized or accidental task updates Aligns with common expectations of a “read-only” experience
0
·
Project
Load More