Instant DSAR scoping in Google Vault from Jira

When a new issue is created in our Jira Privacy or DSAR intake project, run an agent that spins up the Google Vault side of the investigation and posts a scoping estimate back onto the ticket.

The trigger is a Jira issue-created webhook scoped to the intake project (Atlassian supports outgoing webhooks on issue create events, filtered by JQL). When it fires, take the new issue key from the webhook payload and use the Jira Get Issue operation to pull the full summary and description if you need more than the webhook body. Extract three things: the data subject's email, the request type (access, deletion, or portability), and any date range or corpus scope the requester specified. If the email is not present or is ambiguous, do not create a matter. Instead, use Jira Add Comment to ask the reporter to add the data subject email in a structured field, and stop.

Once you have the data subject email, call Google Vault Create Matter with a name that includes the Jira ticket key (for example "DSAR-482 — Jane Doe access request") and a short description linking back to the Jira issue. Keep the returned matter ID. Then for each in-scope corpus (default set: MAIL, DRIVE, HANGOUTS_CHAT, CALENDAR), call Google Vault Count Accounts against that matter with a query using method ACCOUNT and accountInfo.emails set to the data subject's email. Apply the requester's date range via startTime and endTime when they specified one, using RFC 3339 timestamps and the workspace time zone. Count Accounts returns a long-running Operation, so poll Google Vault Get Operation until done is true, then read the account count statistics off the response.

Finally, use Jira Add Comment on the original issue to post a scoping summary in Atlassian Document Format. Include: the request type and data subject you interpreted from the ticket, the date range you applied (or a note that you used the default), estimated message counts per corpus in a small table, a link to the Vault matter, and a suggested next step. Recommend 'proceed to export' when every corpus is under a reasonable threshold (start with 50,000 messages per corpus), and recommend 'narrow the query' when any corpus is above it, with a hint about which one is largest. Keep the tone factual and do not promise any legal outcome, since a human still owns the final decision. Do not run any export or delete operations — this workflow only scopes.