Complicated out of office assignments needed

Diana Fournier 1 year ago in Productivity Management updated by Christine Mellick 6 months ago 5

In Europe it is not uncommon that a user will go on vacation for an extended period of time and will need to set up their out-of-office.  it is also not uncommon that their back-up ends up going on vacation before the user comes back into the office.

We would like to request the following features:

1. If user A inputs user B as a backup and turns on their OOO.  Then user B inputs user C as a backup and turns on their OOO.  All tasks from User A and User B should go to User C.

2. If User A goes on vacation for 3 weeks and wants user B to be their backup for the first week and User C to be their backup for the last week weeks, they should be able to specify.

Enhancement request from our European user community.

Hello Eric - Is there any information on if this is currently being looked at for qualification?

Thanks, Christine

We were just having a conversation with our project management team about having this exact need.  Often times peoples vacations overlap, or because we are a small team, people need to use the same resource as their backup.  

This would be extremely useful for all users. 

Not being able to overlap OOO causes issues regularly for us. Since OOO only covers new jobs opened, we have had to set a users OOO a day or two prior to them being out so any new jobs opened do not sit with the OOO User while they are away, but if that Users backup is out the day prior you can not do this as the backups OOO is on. Having primary/secondary backups or a way for the system to recognize a backup to a backup would be great.

Yes, this is very much needed. As an admin, I spend a lot of time reconciling user's OOO because currently scenario 1 listed above DOESN'T happen  - and it seems logical to users that it would. They assume it does. Very often two people are each other's backups and their PTO overlaps and then a third backup is assigned.

Needed for Scenario 2 as well. User A needs User B to be their backup the first week because User B has capacity the first week, but not weeks 2 and 3 so User C - who has capacity weeks 2 and 3  - needs to be assigned as User A's backup.

This one is so needed.  Currently, it doesn't route at all if user A sets user B as their backup, then user B sets user C as their backup.  It makes no sense why it can't route using the logic above.