Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Written Interviews - Automation should account for PTO #197

Open
VariableDeclared opened this issue Aug 8, 2023 · 4 comments
Open

Written Interviews - Automation should account for PTO #197

VariableDeclared opened this issue Aug 8, 2023 · 4 comments

Comments

@VariableDeclared
Copy link

Hello,

Currently the tool schedules interviews when team members are on PTO, this request is to document this limitation.

As the goal is to turnaround submissions as soon as possible, it would be great if this issue could be resolved,

Thanks,
Peter

@anthonydillon
Copy link
Contributor

HI @VariableDeclared please review the "How is interviewer availability determined?" section of the feature documentation: https://discourse.canonical.com/t/greenhouse-interview-scheduling-automation/2104. When you book PTO, please update your calendar to reflect this status.

@anthonydillon anthonydillon closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2023
@anthonydillon anthonydillon reopened this Aug 15, 2023
@anthonydillon
Copy link
Contributor

Could I please request you reopen the issue and investigate?

@VariableDeclared VariableDeclared changed the title Automation should account for PTO Written Interviews - Automation should account for PTO Aug 15, 2023
@anthonydillon
Copy link
Contributor

The request here is to pull the HRc data locally for each person in the pool and set them as deactivated if they are on PTO. This is tricky as each HL would need credentials to HRc locally to do this.

We do provide the ability to manually manage this which is documented here: https://github.com/canonical/ght#assign-graders-to-written-interviews

@anthonydillon
Copy link
Contributor

Addressed above ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants