I feel this question deserves a new topic.
We’re definitely aware of the downside associated to the restriction of being able to map only one Department to a Pipeline Step. Indeed, we do support mapping multiple Pipeline Step to a single Department but not a single Pipeline Step to multiple Departments. This all about being able to categorize tasks workload properly in a single Department.
We did see this pattern of using a combination of Asset Type or other properties with a single Pipeline Step to map to different Departments. All the solutions that we evaluated to be able to deterministically distribute the task workload to a single department out of many were not clear or easy enough to use. Duplicating the total workload in all Departments does not make sense neither nor distributing it in equally.
In the end we went with what we call a “golden path” approach. As we understand that adopting a 1 Pipeline Step = 1 Department coupling might have some implications, it is really what we recommend (the golden path). Hopefully, adapting to this way of using Pipeline Step and Department is something that can be considered to be able to leverage Resource Planning for those departments.
Hoping this sheds the light on the reason behind the restriction. We’re definitely open to suggestions and ideas related to this though.
Thx again Brandon for dropping your relevant questions here! High value! Definitely worth sharing!