Availability calculation not honoring the amount of hours made availableIssue On the resource_aggregate_monthly table, the availability for some users/months is not being affected by the expected value when changing the number of hours allocated for that user.CauseIf a user is over-allocated for a specific day in the analyzed period, removing the allocated hours above the average FTE settings will have no impact on the user's availability. As an example, for the following scenario, when average FTE is set to 8 hours per day: User: scrum_user_1; Date: 01-01-2018;Currently allocated hours: 10; The user's current availability for 01-01-2018 is 0 hours. By removing 2 hours from any allocation on this user/date, his allocation will become 8 hours, but his availability will not change as the currently allocated hours are still greater than or equal to the average FTE. If you remove 3 hours, the allocation will be reduced by 3, becoming 7, but the availability will only change by 1, becoming 1 hour. ResolutionThis is the OOB expected behavior.