Table of Contents

Class IssueWorkflowSubStateResponse

Namespace
Quilt4Net.Toolkit.Features.Issue
Assembly
Quilt4Net.Toolkit.dll

One phase an issue can be in within a non-terminal state — Doing · In Progress, Doing · To Deploy. Declared by the team's workflow, per state.

public record IssueWorkflowSubStateResponse : IEquatable<IssueWorkflowSubStateResponse>
Inheritance
IssueWorkflowSubStateResponse
Implements
Inherited Members

Remarks

A sub-state rather than another state, because the rules that matter are keyed to the state: claims follow it, the board draws one column per state, and every state needs its own transitions. A sub-state adds the detail and leaves those alone. Moving between the sub-states of one state is not a transition and needs no edge in the workflow.

Always optional: an issue may hold none. The terminal state has no sub-states of this kind — how an issue ended is its Resolution, declared by Resolutions, and that one is required.

Properties

Name

The sub-state's name, unique within its state, and what an issue stores.

public required string Name { get; init; }

Property Value

string

Order

Display order, ascending. Only for display: any sub-state may follow any other.

public required int Order { get; init; }

Property Value

int