Description -
When working on projects, there are times when work is required after hours. For us, this is a lot times related to deployment tasks. In the current setup, the system uses the User, Role, Team, or Project schedules to determine the duration and available dates to work on the tasks. This rigid framework does not allow for allowing work to be performed outside of the normal operating schedule. Proposing the to add the ability for two things:
1. Project schedules to be built on the project itself. This would not require an Admin to create new schedules. This would be similar to an MS Project record....schedules are built into each file.
2. Ability to define whether the Task/Issues follows the Project schedule or the Role, Team, User schedule.
Why is this feature important to you -
The current setup does not allow us to assign tasks to users and have the correct after hours dates stick. Having this new functionality would give the Project Managers the flexibility to create project schedules for each project without needing to coordinate with an Admin, and also allow them to control which schedule is used on tasks or issues.
Additionally, changing the user's schedule to meet the project needs would adversely affect the user's resource capacity.
How would you like the feature to work -
1. Project schedules to be built on the project itself. This would not require an Admin to create new schedules. This would be similar to an MS Project record....schedules are built into each file.
2. Ability to define whether the Task/Issues follows the Project schedule or the Role, Team, User schedule. By default, tasks/issues should follow the existing schedule priority: Role, Team, User, Project
Current Behavior -
Currently, the system uses User, Role, Team, or Project schedules (in that order) to determine task/issue assignment durations. As soon as a user is assigned to to a task, then their schedules takes priority.
https://experienceleague.adobe.com/docs/workfront/using/administration-and-setup/set-up-wf/configure...
