Immutable start/end for tasks or milestones
It would be great to have the ability for a task or milestone to have date properties that can’t be changed. Example is if I put a release date that we have to move toward, we would rather change the scope than the date. Can this be done if not, let’s add it as a feature.
The major purpose of a task link is for rescheduling.
- If we are working on the initial schedule, I don’t suggest to add task link before finalize
- If we are working on rescheduling, if we need to block the link, that means the task link is not useful (or not be created correctly)
Also blocking a task will cause the users confused by themselves:
- When moving a task group, if one sub task be blocked, the behavior will confuse the user
- Also similar when change the project start date
- Also this topic is about task link
-
Andrew Milne commented
Would it be possible to add a fixed task start date flag which would be auto-set on 100% completion. This flag would have an overriding manual control, so it can be set (or reset manually as required). This would stop completed tasks/milestones and planned tasks/milestones (on a specific date) from moving when moving other linked tasks/milestones. Moving a complete group will not affect fixed tasks/milestones (whether complete or not), only moving unfixed tasks.
-
Jm commented
What I’m looking for would be a property of the task start date.
In the existing behavior, if a linked predecessor task is updated to add additional days or the start/end is moved then the subsequent tasks will be automatically moved.
For the behavior I’m suggesting, I want dates that don’t move. Just like you can lock a project, I want a task that is locked and only the items around it can be updated.