Turn a call into GitHub issues

After a client call, Glitchgrab can read the transcript and the screenshots taken during the call, and draft one GitHub issue per thing that was asked for. You check the drafts, correct them by telling it what it got wrong, and only then send the ones you want to GitHub.

Before you start

• The call is recorded and its transcript is ready (see Read a call's transcript).
• The call is filed to a project. File this call to a project first — there is no repo to open issues in.
• The project's repo has the GitHub App installed.
• You are signed in to the dashboard (not as a tester).

1. Draft the issues

If auto drafts is on for the project, the drafts are already here. Skip to step 2. See Auto drafts below.

1. Open Calls and click the call.
2. Above the transcript, under Issues from this call, the panel says what it will read: Reads the transcript and N screenshots from the call, then drafts one issue per thing that was asked for. Nothing reaches GitHub until you say so.
3. Press get issues from this call. It shows reading the call….
4. You will see N draft issues from this call — or Nothing in this call looked like work to file.

Running it again later is read it again, and reading the same call again is free. It replaces the drafts you have not filed, including ones you corrected.

If the transcript is not ready yet: Waiting for the transcript. The assistant reads the words, not the audio.

2. Check each draft

Each draft shows:

• a checkbox — ticked means it will be filed
• the title, labels and body
• the quoted lines from the call it came from, with their times
• screenshots taken during the call at that moment

Untick a draft to leave it out. Press the trash icon (Discard this draft) to remove it.

3. Correct a draft by telling it what's wrong

Easier than editing: say what it misunderstood.

1. On the draft, press that's not what we meant.
2. Type the correction — for example attendance here means WhatsApp check-in, not a biometric device.
3. Press fix it (rewriting…). The draft is rewritten; your note and its reply appear under it as you: and assistant:.

Each correction changes only that draft. After 15 corrections on one draft: This draft has been argued with enough — edit it directly.

4. Send them to GitHub

The bar at the bottom shows X of Y selected. Press create N on GitHub (filing…).

You will see Filed N on GitHub. Filed drafts turn green with a link to the new issue number. A filed draft cannot be corrected here — This one is already on GitHub — edit it there.

Auto drafts

Turn this on and you no longer have to remember the button. It is off by default, and only the project owner can switch it.

1. Open Repos and find the project's card.
2. Press auto drafts off so it reads auto drafts on.

From then on, about 5 minutes after a new call's summary is ready:

• If the client asked for something, the issues are drafted for you. Calls recorded before you switched it on are left alone.
• Anything the team already has open or assigned is left out.
• A call with no asks, such as a wrong number, gets no drafts and no message.
• The call's row on Calls shows N drafts to review.
• The person who made the call gets one email and one WhatsApp. If a tester took the call, or nobody placed it, the project owner gets them.

File from WhatsApp. Press Show issues on the message. Each issue arrives with what was asked and the client's own line, followed by a File issue list. Pick one to file it and get the link. To correct one first, open the call.

Nothing is filed until a person chooses it.

Limits and messages

• 40 calls per project per month can be read with the button — This project has read its limit of calls this month. Reading a call you already read does not count again. Auto drafts do not count towards this limit.
• This call has no transcript yet.
• Could not read this call. — try get issues from this call again in a minute.
• GitHub App not installed on this repo — reconnect in Connect Repo to grant access — install the App from Repos → install app (there is no Connect Repo screen). See Connect your GitHub org.
• Could not file "<title>" — that one draft failed; the others still went. Try again.

Why screenshots from the call

A screenshot cannot be taken of a moment after the call has ended. The bot grabs frames during the call — when someone shares their screen, those frames show what they were pointing at — and the drafts use them so the issue shows the exact screen that was discussed.