How it works / Concepts
Tasks
The fix itself takes twenty minutes. Getting to it takes the morning. You reproduce the bug, find the code, write the test, run the checks, open the pull request and explain it all in the thread.
A Task is a piece of work you hand to Jigward in your own words. Jigward works it through to a report.
What changes
-
Before: “Rides to Moon Base 2 cost ten times more after midnight,” in Slack.
With Jigward: Draft pull request #36, with a test that failed first and a report in the same thread.
-
Before: A Jira issue assigned to Jigward.
With Jigward: The issue in review with the report as a comment, and never moved to Done.
-
Before: “Review this, please,” on a colleague's pull request.
With Jigward: Comments on the lines that need them, never an approval or a block.
-
Before: “Check booking on staging in the browser.”
With Jigward: A recording, console log and screenshots kept with the Task.
How it works
-
Given
On the web, from a Chat card, in Slack, on Jira, on a pull request, by a Duty or from an Application's page. It is the same Task wherever it came from.
-
Worked
Jigward reads first. It takes an isolated workspace only when the work needs a working copy, a build or tests.
-
Asked, when it must be
Jigward asks only when it cannot go on responsibly, for example when data would be lost, the request reads two ways, or access is missing. It asks one question, with options.
-
Reported
The report goes back where the Task was given. It says what Jigward found, changed and decided, and how it checked. A change arrives as a draft pull request that a person merges.
What it can do
-
Fix it with a test first
For a bug, Jigward writes a test that reproduces it and sees it fail, then fixes the code and sees it pass.
-
Run the checks CI runs
It runs the repository's own checks on the change it proposes, so its pull request does not arrive red.
-
Open a draft pull request
Its pull request is one branch and one description in Jigward's words. Feedback on it continues the Task.
-
Record every decision
Where reasonable choices differ, it records what it chose, what settled it and what that rests on.
-
Work in a real browser
It signs in with the Context's browser profile and keeps the recording, console log, network log and screenshots.
-
Ask one precise question
Two to four options when it already knows them, or your own words. A question is not a failure.
How it connects
- Chat A Chat works a Task out with you before it exists.
- Duties A Duty's wake gives a Task when reading is not enough.
- Applications An Application's page can start a Task once it is allowed to, and only after you confirm.
- Contexts A Task keeps its Context for good, and can involve none, one or several of its repositories.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.