Expand description
Normalised entities.
These are our schema, not Tracker’s. --json emits these so that scripts
keep working across Tracker API changes; --json-raw exists for the cases
where someone genuinely needs the upstream payload. Every unmapped field is
preserved in extra, which is also where a queue’s custom fields arrive.
Structs§
- Attachment
- One attachment of an issue.
- Change
- One recorded change to an issue.
- Checklist
Item - One line of an issue’s checklist.
- Comment
- One comment, reduced to what output shows.
- Dict
Entry - One entry of an organisation-wide dictionary: an issue type, a priority, a status or a resolution.
- Entity
- A project, portfolio or goal.
- Field
Change - One field, before and after.
- Issue
- An issue, normalised.
- Link
- One edge from an issue to another issue.
- Page
- One page of results plus the totals needed to say “shown N of M”.
- Person
- A person, in full.
- User
- A person, reduced to what output ever shows.
- Worklog
- One entry in an issue’s worklog.
Enums§
- Link
Kind - How two issues relate. Rendered on every issue view, because “what blocks this” is the question an agent asks right after “what is this”.