Use cases

What teams hand to Jigward.

Situations from an engineering team's week, each with a short film. Someone asks where they already work, Jigward does the legwork across the code, the logs, the tickets and the browser, and the answer comes back with what it rests on.

How every case works

Ask where you already work

A mention in Slack, a Jira issue assigned to Jigward, a review comment on its pull request, or a Duty that wakes on a schedule.
Jigward does the legwork

It reads the code and the schema, searches the logs, reproduces the problem in a browser or a test, across every repository it was given.
The answer comes back where you asked

A reply in the thread, a draft pull request, a comment-only review or a Jira issue, with the evidence kept on the Task.
The team decides

Merging, deploying, rolling back and what to tell a customer stay with people. Every case says what Jigward did not check.

All use cases

Search use cases

Who asks How it arrives Jigward uses

12 use cases

When production breaks

Errors doubled after a release. Was it the deploy?

The error rate doubles the day after a release, two dashboards point two ways, and someone has to decide whether to roll back.

Jigward uses: SlackTasksAWS CloudWatch LogsGitHubWorkspace

A mention in the incident channel Film, 1 min 41 s
When production breaks

38 alerts overnight. One was real.

With no night shift, the alerts channel fills with noise overnight, and the engineer on call either reads all of it at dawn or mutes it and misses the real one.

Jigward uses: SlackDutiesMemoryTasksAWS CloudWatch Logs

A direct message to Jigward in Slack Film, 1 min 47 s
When production breaks

Third time in three months. Didn't we fix this in August?

The same page fires for the third time in three months, and the fix agreed after the first one still sits in an action item nobody has had time to build.

Jigward uses: SlackInitiativesAWS CloudWatch LogsTasksGitHubWorkspace

A direct message to Jigward in Slack Film, 1 min 46 s
When production breaks

Checkout is fixed. Which customers did we hit?

The outage is fixed, but support does not know exactly whom to email and finance does not know who may need a credit.

Jigward uses: SlackTasksAWS CloudWatch LogsApplications

A direct message to Jigward in Slack Film, 1 min 44 s
Before a release ships

Every check is green on a column drop. Does anything still read it?

A cleanup pull request drops an old column and passes every check, but the checks cannot see the other repositories and the old instances that still read it.

Jigward uses: SlackTasksProject knowledgeGitHubMemoryInitiatives

A mention in the team channel Film, 1 min 48 s
Before a release ships

640 regression cases, two testers. What does this release change?

Running the whole regression sheet takes a week, so testers guess what to skip, and nobody records what went untested or who accepted it.

Jigward uses: SlackTasksGitHubMemoryWorkspaceBrowser

A mention in the QA channel Film, 1 min 59 s
Keeping main healthy

The same test keeps breaking main. Flaky, or a real bug?

The same test keeps turning main red, the team reruns it until it passes, and nobody finds out why it failed.

Jigward uses: SlackDutiesTasksWorkspaceProject knowledgeGitHub

A standing Duty, asked for in Slack Film, 1 min 47 s
Keeping main healthy

The same review comment on every pull request. Will this one stick?

Reviewers repeat the same correction on pull request after pull request, because the convention lives only in their comments.

Jigward uses: JiraGitHubWorkspaceMemoryInitiativesSlack

A review comment on Jigward's draft pull request Film, 1 min 33 s
When someone needs an answer

Works on staging. Not for the customer.

A customer's import keeps failing, engineering cannot reproduce it on staging, and the ticket has bounced between support and engineering three times.

Jigward uses: JiraCustom APIBrowserAWS CloudWatch LogsGitHubSlack

A Jira issue assigned to Jigward Film, 1 min 57 s
When someone needs an answer

Bug or expected? Before the 3 PM call.

A customer cut seats, 15 of their users lost access this morning, and only an engineer seems able to say whether it is a bug before the afternoon call.

Jigward uses: SlackCustom APIGitHubBrowserInitiativesMemory

A mention in the support escalations channel Film, 1 min 51 s
When someone needs an answer

A critical advisory landed. Are we affected?

A critical advisory lands, a search of one build file has already marked billing "not affected", and a customer needs an answer this week.

Jigward uses: SlackProject knowledgeGitHubJiraWorkspace

A mention in the security channel Film, 1 min 48 s
When someone needs an answer

Stripe says paid. The app says free.

At month-end, Stripe and the product disagree on who is paying, finance can see two totals but not which accounts are wrong, and a paying customer is already locked out.

Jigward uses: SlackCustom APIApplicationsAWS CloudWatch LogsJiraDuties

A direct message to Jigward in Slack Film, 1 min 59 s