Jobs

Jobs are lightweight tickets that live next to the files they're about. Because they live in Grixel, the backlog stays with the work instead of drifting off into a separate tracker, and you only see jobs for the areas you can access.

#Your worklist

Start here — what's assigned to you, what you created, and what's unassigned nearby:

grixel jobs --mine

#Look at a job

grixel job show job000007

You'll see its type, title, status, who it's assigned to, the path it's anchored to, and any custom fields your team uses.

#Create a job

Your team defines the available job types and their fields. Check what's available first, then create one:

grixel job spec                                    # the types, statuses, and fields you can use
grixel job create -type bug \
  -anchor /companies/acme/games/seasonal \
  -title "Hero texture seams on consoles" \
  -field severity=major

#Update a job

grixel job update job000007 -status fixed

A job can only move between statuses in the ways your team's setup allows — grixel job spec shows the legal transitions.

#Link a job to the change that resolves it

When you submit a change that addresses a job, cite it:

grixel submit --job job000007 -m "fix the seams on the hero texture"

Now the job and the change point at each other, so anyone looking at either can find the other.

#Watching activity

grixel job events        # a feed of recent job activity in an area

This is handy for dashboards and automation that need to react to job changes.