How it works / Concepts
Contexts
The question comes up in Slack, the bug lives in Jira, the fix lands in GitHub, and the reason behind it stays in one person's head. Every new tool, and every new person, starts from zero.
A Context is one lasting area of work. It holds its repositories, its Tasks, Chats, Duties and Applications, and what Jigward knows about it.
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: Five people explaining the same backend to five different tools.
With Jigward: One Jigward that already knows orbit-cab, answering all five.
-
Before: A decision made in a thread and forgotten by Friday.
With Jigward: What the work settled, remembered for the Context, with where it came from.
-
Before: The fares backend and the pilots' app in one long list of everything.
With Jigward: One Context for each, with its own repositories, Tasks and Duties.
How it works
-
Add the repositories
An admin adds repositories from the connected GitHub account. Each one belongs to exactly one Context.
-
Jigward reads them
It builds an understanding of each repository, including the database schema its migrations build, the API from its OpenAPI document, and its dependencies.
-
The team works in it
Members give Tasks, ask in Chats, set Duties and build Applications there. A Slack channel or a Jira project is named with the Context it belongs to.
-
It remembers
What a Task or a Chat establishes about the product is kept for the Context, and the next piece of work starts from it.
What it can do
-
Hold the repositories of one area
Every repository is in exactly one Context, so the work never wanders into someone else's code.
-
Remember for the team
Memory written by Tasks and Chats, with its reach, its source and what it rests on.
-
Keep the channels in line
Slack channels and Jira projects are named with a Context, so work given there lands in the right place.
-
Keep its own connections
Browser profiles and custom integrations belong to one Context. GitHub, Slack and Jira stay the organization's.
-
Divide the work, not the people
Every member of the organization can reach every Context. There is nothing to invite anyone into.
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.