jigward
Sign in Early access
Explore Jigward

How it works / Concepts

Applications

Every team has the spreadsheet nobody owns, like the pull request tracker, the release checklist or the list of test cases. It goes stale by Wednesday, and nobody has a sprint to spare to build the real tool.

An Application is a small internal tool Jigward builds for a Context. It is a page, a database of its own, and named actions the rest of Jigward's work can use.

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: A spreadsheet of open pull requests, updated by hand.

    With Jigward: Launch pipeline, with every pull request from the pad to the Moon, refreshed each weekday morning.

  • Before: The QA lead's release checklist in a document.

    With Jigward: A list of cases with a button that starts a browser check once you confirm its words.

  • Before: Two CSV exports and a question for the Friday review.

    With Jigward: A board drawn from them, which says it shows only what the files hold.

  • Before: Asking around for what shipped this week.

    With Jigward: A board that moves by itself whenever a Task in the Context ends.

How it works

  1. Say what it is for

    Ask in a Chat or use New application. Give it a name, say in your own words what it is for, and choose team or personal.

  2. Jigward builds it

    It builds the page in Jigward's look and your theme, with a database of its own. That database changes in numbered steps that are kept.

  3. It fills it

    Data comes from a custom integration, from a CSV attached in its conversation, or from what people do on the page.

  4. It keeps it working

    Ask for a change in the conversation beside the page. Every version stays and can be restored.

What it can do

  • A page with its own data

    Tables Jigward designs, and operations that change them, each run recorded.

  • Fill it from your APIs

    A fetch over one of the Context's custom integrations. The credential stays where it is, and neither the page nor the application sees it.

  • Move when work ends

    An action can run whenever a Task in the Context completes or breaks off, with no page open.

  • Start a Task from the page

    Once its creator or an admin allows it, and only after the person clicking confirms the exact words.

  • Versions you can restore

    Every version that went live is listed with a summary, and any one can be made live again.

  • Used by Jigward too

    In a Chat, a Duty or a Task, Jigward reads what a team Application holds and calls its actions.

How it connects

Keep reading

Next concept Contexts One area of work the whole team shares with Jigward. How Jigward works

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.

Request early accessRequest a demo by email

Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.