Enum AnalyticsCommand 

pub enum AnalyticsCommand {
    Burndown {
        args: AnalyticsScopeArgs,
    },
    Projection {
        args: AnalyticsScopeArgs,
        as_of: String,
    },
    Export {
        args: AnalyticsScopeArgs,
        as_of: Option<String>,
        output: Option<String>,
    },
}

The tix analytics subcommands (mission burndown-scope-analytics-01M3C9J1, WP05).

A thin adapter over the shared analytics DTOs. The daily fold, the unit conversion and the projection live in crate::analytics, and the versioned chart document is WP04’s (crate::commands::export::chart_document), which every verb here calls rather than re-composing. This enum owns only the spelling of the surface: the scope, the period and the mode/unit are always explicit, and no flag here can change an issue, a cycle date, a milestone or a snapshot.

Variants

Burndown

Print the daily remaining/completed series for one cycle or milestone

A tab-separated table with a date column followed by the point’s own fields — scope_total, remaining, completed, scope_added, completions — and the day’s coverage. A value the record cannot support is -, never a zero, and a day with no recorded history is unknown or coverage_limited. The scope, period, mode, unit, formula version and coverage tally print above the header row, and the findings render to stderr with their remedies.

Fields

args: AnalyticsScopeArgs

Projection

Print the read-only end-date forecast over one cycle or milestone

The planning end date is the scope’s own (--to overrides it) and --as-of is the caller’s day, never a clock. A forecast the record cannot answer prints its status (insufficient_data or unknown) with - for every value it could not derive — no completion date is ever invented, and no planning date or issue changes.

Fields

args: AnalyticsScopeArgs

as_of: String

The forecast origin, a YYYY-MM-DD calendar date

Export

Write the deterministic local chart document (WP04’s target)

The document goes to stdout, or to --output through the atomic export writer the other local targets use. --mode is required: the document states the mode it was folded in, so a default would be a guess about which arithmetic produced the numbers. --as-of asks the same document for a forecast. The remote gitlab/linear namespaces are never consulted and cannot collide with a chart document.

Fields

args: AnalyticsScopeArgs

as_of: Option<String>

Ask the document for a forecast at this origin, a YYYY-MM-DD calendar date

output: Option<String>

Write the document to this path instead of stdout

Trait Implementations

impl Clone for AnalyticsCommand

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for AnalyticsCommand

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl FromArgMatches for AnalyticsCommand

fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

fn update_from_arg_matches_mut<'b>( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

impl Subcommand for AnalyticsCommand

fn augment_subcommands<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate Self via FromArgMatches::from_arg_matches_mut

fn augment_subcommands_for_update<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate self via FromArgMatches::update_from_arg_matches_mut

fn has_subcommand(__clap_name: &str) -> bool

Test whether Self can parse a specific subcommand