Brainstorm Screendoor integration

[jrubenoff]

Outcome

• Screendoor reviewers can easily see whether an interview was conducted, scheduled, cancelled, etc. with an applicant.
• Admins and interviewers can easily access an applicant's Screendoor response when an interview takes place.

  Structure

• Add interview details to the activity feed
• Add a link to the applicant's Screendoor response on everything: calendar invites, confirmation emails, the admin dashboard, etc., so it's impossible to miss

More TBD...

[ajb]

This all sounds good to me.

On Mon, Jul 18, 2016 at 11:16 AM, Josh Rubenoff notifications@github.com wrote:

Outcome

• Screendoor reviewers can easily see whether an interview was conducted, scheduled, cancelled, etc. with an applicant.
• Admins and interviewers can easily access an applicant's Screendoor response when an interview takes place.
• Nice to have: if staff, who live in Screendoor and aren't necessarily aware this app exists, lose their invite email, they can easily retrieve their meeting details from Screendoor.

Structure

• Add interview details to the activity feed
• Add a link to the applicant's Screendoor response on everything: calendar invites, confirmation emails, the admin dashboard, etc., so it's impossible to miss
• Let reviewers download their calendar invites in Screendoor, or (in our v2?) see it on a new "Calendar" page

More TBD... curious what @ajb https://github.com/ajb thinks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/dobtco/gbas/issues/22, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNiLZqK7U578McPTLwWAg8Id00s8ozCks5qW8LhgaJpZM4JO_P2 .

Adam Becker (951) 9-BECKER @AdamJacobBecker

[jrubenoff]

I brainstormed a few ways we could go about this, and came up with two approaches.

1. Log everything in the activity feed. That would look something like this.

   One problem: we'll need to add a large number of events to achieve the outcome for interviews that were never conducted, or never fully booked. That clogs up the feed. We could solve this by hiding some events by default, and adding a "show all events" option to the feed, but that adds complexity.

   Discoverability is also problematic. Since the activity feed is below the response, interviewers might never see these events.

2. Show an "interview status" alert for invited candidates. The alert would appear above the response, like this.

   Depending on the status of the interview, the alert would have different states. Here's my attempt at listing all of them. After the interview is done, we add a single event to the activity feed.

   I like how this solution knows whether you're invited, not invited, or an admin, and shows you the most relevant information accordingly. It is hard to do that with events in the activity feed.

   One problem: it might take too much time to implement every state. But based on prior work on the activity feed, maybe the first approach will also take a lot of time?

   Another problem: if we're only adding one event to the feed, that might pose a compliance / auditing problem. But I guess we could tackle that in dobtco/screendoor-v2#3321.

[ajb]

The mockups you posted are awesome. I really like both ideas... in fact, if we imagine that we were building this functionality into Screendoor itself, we'd probably implement both activity feed items as well as a "current status" notification!

However:

• To do this properly, I'll need to design a new Screendoor API for "integrations."
• I think that this could safely be left out of our MVP.

[ajb]

This issue was moved to dobtco/scheduler#14