The joining and leaving date in the team does not affect the "available hours" column and plannability. If the person's leaving date is set for a Wednesday and you filter for the team in which the leaving date is set, their available hours for the week should only be 3 days worth of hours, but the planner shows full-time availability.
The Resource Planning view does not show users who at the specified time period are not active in any teams - so the number of available hours should also take the team membership into account I think.
Also if someone is in multiple teams, the Resource Planning view allows you to plan time for them even after the leaving date, regardless of the team filter. If you are only in one team and the leaving date is set, the planner will give a warning and won't allow you to plan after the leaving date. I think if you are in multiple teams, but you filtered for a specific team, you shouldn't be able to plan time after the leaving date in that specific team.
Guest
| Tempo Products | Tempo Planner |
| Tempo Platform | Cloud |
Same is for joining date the other way round. If a user has a joining date in future he should not have any availability in the presence.
The logic of calculating availability values should also consider the joining date.
The current behavior through an example:
today is Tuesday
we are planning for this week
if the leaving date for a user is set to Monday, the user is not show at all (this is correct)
if the leaving date for the user is set to Tuesday, the planning shows "Available hours: 32" -> should be 8 hours -> why does this not take the leaving date into consideration when the logic is clear : planning makes sense until the leaving date (that's why users are hidden if the leaving date is in the past)