One common use case for clipper is multiple activities that are performed in serial. It is difficult to accomplish this with the current set of scheduling goals, but is fundamentally a simple operation. Please add a capability to treat a specified sequence of activities like an activity, so things can be scheduled relative to it and it can be scheduled with recurrence and cardinality rules. Additionally, there should be a mechanism for providing relative timing within the sequence to encode wait times between activities.
The project should have the flexibility to encode these types of rules in scheduling rather than as decompositions because having too many decompositions clutters the timeline and obfuscates the lineage between activities because there are too many relationships.
One common use case for clipper is multiple activities that are performed in serial. It is difficult to accomplish this with the current set of scheduling goals, but is fundamentally a simple operation. Please add a capability to treat a specified sequence of activities like an activity, so things can be scheduled relative to it and it can be scheduled with recurrence and cardinality rules. Additionally, there should be a mechanism for providing relative timing within the sequence to encode wait times between activities.
The project should have the flexibility to encode these types of rules in scheduling rather than as decompositions because having too many decompositions clutters the timeline and obfuscates the lineage between activities because there are too many relationships.