How it works / Concepts
Duties
Someone has to read the pilots' channel before stand-up, check whether pull request 37 got its review, and see that the asteroid weather service still answers. Usually that someone is busy, and nobody does.
A Duty is a standing instruction Jigward carries out at a set time, once or on a rhythm.
Context
One lasting area of work, shared with Jigward.
- Repositories
- The code, database schema, APIs and dependencies.
- Project knowledge
- What earlier work established, with its sources.
What changes
-
Before: Remembering to read #pilot-notes before stand-up.
With Jigward: A report at 8:30 every weekday, sent only when something sounds like a bug.
-
Before: Refreshing pull request 37 to see whether anyone reviewed it.
With Jigward: A check every hour that ends by itself once the pull request is merged.
-
Before: A note in the channel that is really a bug.
With Jigward: A Task the Duty gave, with tests.
-
Before: Asking every Friday whether a connected service still works.
With Jigward: A wake that calls it, and reports a problem only when there is one.
How it works
-
Say what, and when
Use the Duties page, or ask in a Chat and Jigward makes the Duty itself. It can run once, every 15 minutes or more, or on chosen weekdays, in a named time zone.
-
It wakes and reads
A wake needs no workspace. It reads the Context's repositories, what Jigward remembers, public pages, custom integrations and team Applications.
-
It decides what is worth saying
Each wake ends with nothing new, a report or a problem. A finding that has not changed is not reported again.
-
It hands off real work
When the instruction needs a change or a test run, the wake gives an ordinary Task.
What it can do
-
Wake on a rhythm
Once, every interval, or on weekdays at a time of day. 9:00 in Berlin stays 9:00 in Berlin through summer time.
-
Say only what changed
A wake knows the last report it gave, so an unchanged finding stays quiet.
-
Give a Task
When reading is not enough, the wake gives a Task, or continues the one it gave before.
-
Use your integrations and tools
It calls what a custom integration offers and the actions of the Context's team Applications.
-
Know when to stop
A check Jigward makes for itself always has an end, and ends early once its goal is reached.
-
Keep every wake
Each wake is kept with its instruction at the time, its outcome, the Task it gave and where its report went.
How it connects
- Chat Jigward gives a Duty from a Chat when the conversation calls for it. Its reports come back to that Chat.
- Tasks A Duty gives a Task when reading is not enough, and reports into the Task it came from.
- Applications A wake can call the actions of the Context's team Applications.
- Contexts Everyone in its Context sees and edits it, and it never reaches another Context.
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.