Expand description
HTTP layer against the Tracker REST API.
We talk to the API directly instead of using the official Python-era client:
see docs/adr/0004-own-http-client.md.
Modules§
- duration
- Durations, in the two forms this tool has to speak.
- error
- Typed API failures.
- models
- Normalised entities.
- parse
- Turning Tracker’s payloads into our models.
- query
- Building Tracker query strings from filter flags.
Structs§
- Auto
Action - A change Tracker applies on a schedule to whatever matches a filter.
- Automation
- What changes issues in a queue without anybody touching them.
- Blueprint
- The parts of an existing queue a new one can be built from.
- Board
- A board, reduced to what a listing shows.
- Client
- A configured Tracker client.
- Client
Config - Everything the client needs to address one organisation as one account.
- Field
Options - What a constrained field will accept.
- Field
Spec - One field’s definition: what it holds, whether it can be written, and what values it accepts.
- Macro
- A canned change somebody applies by hand from the issue page.
- Queue
- A queue, reduced to what a listing shows.
- Queue
Field - One field of a queue.
queue fieldsis how a caller learns the keys that--fieldsand--setaccept, so the key matters more than the name here. - Queue
Settings - A queue with the settings that decide what an issue in it starts as.
- Sprint
- One sprint of a board.
- Template
- One template, reduced to what a listing shows.
- Transition
- A workflow transition available from the current status.
- Trigger
- A change Tracker applies the moment something happens to an issue.
- Unreadable
- One section that could not be read, and why.
- Version
- A release a queue tracks work against.
Enums§
- Dictionary
- Which organisation-wide dictionary to read.
- Template
Kind - Which templates are being asked for.
Constants§
- DEFAULT_
BASE_ URL - Default API root. Overridable so tests can point at a
wiremockserver.