Dynamic Member Scheduling
D
Dustan Minnig
I'd like a way to select multiple resources available to schedule, with the ability to select whether all members need to be scheduled at the same time, or if any one individual should be scheduled.
This would allow our scheduler to select the appropriate resources quickly for each ticket. Our company does a lot of different type of work, and has a lot of situations where a 'hard-coded' team does not fit.
This would be selectable for each scheduling interaction inside the TimeZest pod. It appears the only way to get close to this is to create teams for multiple combinations of people, which gets very messy very quickly.
Log In
Jason Casuga
Merged in a post:
Options Scheduling
J
Josh Campbell
So the Panel Scheduling is great but that is more of an AND and I think it would be good to have an OR option too.
The issue I am running into is I have a tech who is quarantined because of COVID-19 and is feeling fine to still work from home, but cannot go onsite. I have a lot of Teams I have created that he is a part of but I cannot use those teams for onsites because I can’t have them go to him. Creating a different Team is not an easy solution because we have had this a few times where someone has felt ill so they get tested and we say no onsites until we get the results. So I wouldn’t want to have to make a new team each time.
It would be nice in the panel scheduling section if I was able to choose AND or OR when scheduling. That way I could just list the other techs in the group besides him and select OR and send it out.
Jason Casuga
Merged in a post:
"Any" or "All" toggle for scheduling
M
Michael Cluney
A switch that changes the parsing behavior when adding multiple resources would be helpful. By default it schedules appointments with all of the teams or users defined in the pod. It would be nice to be able to change this behavior, so we can add multiple people or teams for the system to choose from on the fly.
E
Elizabeth McBrearty
This would be so helpful for us as well to be able to schedule tickets based on dynamic/changing availability and ticket type. Sometimes I only want Tech A and B to be options for scheduling on a ticket or Tech B and C for another ticket but without creating teams for all possible combinations.
L
Liz Fornero
This would be incredibly helpful to have to provide customers with more flexible time options based on multiple users'/teams' availability!
J
Josh Campbell
Feel like this would be a easy add on and have seen a few requests that are similar.
D
Damian Bailey
I have to generally agree with Josh here - the ability to mark a user for remotely only vs on site's, plus the other commenters suggestions below would be a huge plus. Unsure if this would be best set as a field in CW per user, or set in TimeZest directly, but would be a win regardless.
R
Rob Calvert
I like the explanation from Josh at the start of this. But I come at it from a different thought...and this may be IN ADDITION to his thoughts...could a NOT be implemented? Same context, 4 engineers in the team, one of whom is remote only on COVID restrictions. Add the team (which includes said restricted tech) and the phrase NOT and the tech's name? The result is anyone on the team just NOT that tech.
G
Gerwai
Rob Calvert: I can't wait until we don't have to talk about Covid anymore! But, since that isn't going to happen anytime soon, a question. It appears your thoughts also relate to onsite versus remote appointment types, correct?
Josh Campbell: What about a member/user field that identifies whether a person can be scheduled for onsite and/or remote appointment types? That would save you work and clicks. It could also solve for more use cases.
J
Josh Campbell
Gerwai: and Rob Calvert both of these are great ideas. Thank you for the feedback and suggestions.
R
Rob Calvert
Gerwai: Great question, but I actually foresee using this in other ways as well. We have Mac and Windows teams, iOS and Android teams, etc. Sometimes we'd like to say well that is an advanced need, and that tech isn't quite seasoned enough; choose the team, but NOT that team member. The use of boolean logic for this means the options would be extremely flexible.
J
Josh Campbell
Rob Calvert: I agree. I can see several uses for that outside of COVID and onsites.