Set preferred team
rillsoft_project_team_preference_setMarks a team as a project's preferred team, setting a preference that inherits to subprojects and presets resource candidate filters. Use it to narrow capacity planning supply, not to assign tasks.
Instructions
Marks a team as the preferred team of a project or subproject. This is not an assignment but a preference, carrying neither utilization nor productivity: it is inherited by every subproject below, it presets the team filter in rillsoft_task_resource_candidate_list and in the dialogs, and it narrows the supply in the capacity view split by project. projectUuid addresses the main project (empty) or any subproject. Read it back through rillsoft_project_tree_get (preferredTeams[]). Team assignments on individual tasks do not exist in this contract; people are assigned through rillsoft_task_employee_assignment_set. In a portfolio projectUuid names a project or a subproject inside it, as in a single project; the portfolio itself carries no preferred team (the user interface offers none there), so an empty projectUuid is refused. One undo step.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | id of the team from rillsoft_resource_pool_catalog_list with types:["team"] | |
| projectUuid | No | UUID of the project or subproject that carries the preference; empty = the main project |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wbs | Yes | WBS code | |
| name | Yes | name | |
| uuid | Yes | UUID of the element | |
| start | Yes | start, DD.MM.YYYY hh:mm | |
| finish | Yes | finish, DD.MM.YYYY hh:mm | |
| number | Yes | number of the element; unique even for split tasks | |
| preferredTeams | Yes | the preferred teams of the project or subproject after the change |