Namespace Quilt4Net.Toolkit.Features.Issue
Classes
- AddIssueLinkRequest
Declares a dependency from one issue to another. Requires an API key carrying the
issue:writescope.
- CreateIssueRequest
Creates an issue. Requires an API key carrying the
issue:writescope.
- IssueClaimResponse
Who says they are working on an issue, and from which machine.
- IssueLinkResponse
One outgoing dependency from the issue that carries it, to the issue named by TargetNumber.
- IssueReferenceRequest
One reference to write onto an issue. See IssueReferenceResponse for what the fields mean.
- IssueReferenceResponse
One reference from an issue to where it came from, or to the ticket it is.
- IssueResponse
One issue on a team's tracker.
- IssueServiceException
Thrown when the Quilt4Net server rejects an issue-tracker call.
- IssueWorkflowResolutionResponse
One way an issue can end, declared by the team's workflow —
Done,Won't do, and whatever else a team needs.
- IssueWorkflowResponse
A team's issue workflow: the states an issue may be in, and the moves between them that are allowed. One workflow governs every issue on the team.
- IssueWorkflowStateResponse
One state in an IssueWorkflowResponse.
- IssueWorkflowTransitionResponse
One permitted move in an IssueWorkflowResponse.
- RoadmapEdgeResponse
One drawn dependency between two items on the map.
- RoadmapItemResponse
One issue as it appears on the map.
- RoadmapResponse
The roadmap, already laid out. This is the shape the view component draws.
- RoadmapRouteResponse
One lane of the roadmap.
- SetIssueStateRequest
Moves an issue to another state. Requires an API key carrying the
issue:writescope.
- SetIssueWorkflowRequest
Replaces a team's issue workflow. Requires an API key carrying the
issue:writescope.
- UpdateIssueRequest
Replaces an issue's editable fields. Requires an API key carrying the
issue:writescope.
Interfaces
- IIssueService
Reads and writes a team's issues on the Quilt4Net server.
Enums
- IssueEffort
Rough size of an issue. Effort is the one field a roadmap restates from the underlying record, because quick wins — small items with nothing pointing at them — are invisible without it.
- IssueImportance
How much an issue matters, paired with IssueEffort to give the house ordering rule: importance first, then effort ascending — highest impact for least work.
- IssueLinkKind
The kind of dependency one issue declares on another. These are the three edge kinds a roadmap may draw; an edge that is none of them is not an edge, and is left off the map.
- IssueReferenceRole
What a reference is for. Two jobs hide inside "where did this issue come from", and they have opposite tolerances for going stale, so the field says which one is meant rather than leaving every reader to guess from the Kind.
- RoadmapBand
Where an issue sits on the roadmap's order axis. The band is a suggestion the reader may ignore, which is why it is drawn as a soft background band rather than as an arrow — ordering suggests, while IssueLinkKind edges constrain.
- RoadmapStateKind
Where an issue's state sits in the team's workflow, reduced to the three shapes a map can draw.