New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedule : task-groups dont represent sub-items #368
Comments
We improved the first point by adapting the main bar when a bar below is moved. Linking tasks to task type is a tedious question. Because most of the time people start with a rough schedule and after that set deadlines for each task. They don't expect to set task firsts. The other question is: should the rough schedule be updated if the task planning doesn't match? |
Ping @gwen |
Hi @frankrousseau, How nice that you've been able to look into this so quickly. I like how the task-group bar is now updated to represent the sub-tasks. May I suggest to disable changing the length of the task-group bar? That way it will remain linked to the sub-tasks. It would be cool if moving the task-group bar would also move all sub-tasks as if they were parented to the task-group. On a side-note, has it always been this sluggish to drag? It's much more responsive on the task-type schedule. (Schedule on the bottom part of the previous image I attached) Unfortunately something goes wrong in the link between the schedule and the main schedule. If I move something on it also moves in the other but the values aren't the same. |
Hi @bartdriedee, Some users don't use the sub-tasks on the production schedule; that's why we allow changing the length of the task-group bar. I can't reproduce your bug with the back and forth of the production schedule and the studio schedule. The sub-tasks are not linked to the main-tasks bar; that's why they don't move when you adjust the main-task bar on the studio schedule. We have added this feature on our roadmap: https://cgwire.canny.io/ |
Problem:
Task-groups (e.g. Offline or Rigging in the image above) is not linked to the sequences it represents. When task-groups are collapsed the may give an incorrect representation of the schedule. This is inconvenient in the "schedule" page but problematic in the "main schedule" because there it only displays the task-groups.
Solution:
Link the task-group start and end to the earliest start and latest end of the sub-items. Or even nicer letting the task-group be a flattened version of the sub-items. Linked images below illustrate what I mean.
The text was updated successfully, but these errors were encountered: