Is there a way to lock a project down from any further updates by team members? For example, some platforms allow admins or certain people to lock the project to prevent changes to project details (or at least the schedule) after a project details are finalized.
Here is my current need/use case as a Product PM:
We'd like to add Feature A to our desktop product so we open Project A and begin vetting solutions. In that process, we learn another product manager is vetting a similar feature, Feature B, for Mobile under Project B. Since both solutions serve similar needs, we decide to adjust course and pursue a broader scope solution that encompasses the needs of both PdMs. There is no way to combine the history and details of both projects into a single project so I have two options: open a new project for both and lose all history in the project or choose one of the existing and only risk losing some history. Either way I'm going to lose something. I decide to close out the project with the least work completed to date (Project A), add a [cancelled] prefix to Project A, rename Project B to encompass both solutions, and send an email instructing everyone:
"Please only use Project B going forward. Do NOT post or update Project A!"
Well, no matter what both projects continue to show up in search, people have notifications in their emails they can respond to, etc. No matter how hard I try updates and posts and files continue to be added in both projects even though one is very clearly cancelled.
This is very frustrating and is easily solved by either a combine project history feature or lock project for all updates feature. This is also a project management best practice as, without it, there's nothing to stop someone from (either accidentally or intentionally) changing historical data after the fact. Yes, it would show in the log that it was changed but why allow changes at all?
