Dashboard
2 Scenarios / 8
Parameters

Scenarios

Configure allocation scenarios and understand data sources

Active Scenario
How Scenarios Work
Scenarios provide context for allocation decisions. The selected scenario influences:
  • Default threshold values
  • Risk assessment weights
  • Compliance requirements
  • Audit documentation levels
Data Sources

In a production environment, MCAT integrates with your existing tools to extract decision context automatically:

Ticketing Systems
  • Jira / Linear / GitHub Issues - Issue type, priority, story points, labels
  • Extracted features: complexity estimate, affected components, linked incidents
Version Control
  • GitHub / GitLab / Bitbucket - PR size, files changed, test coverage
  • Extracted features: code churn, author experience, review history
Security & Quality Tools
  • SonarQube / Snyk / Dependabot - Vulnerability severity, code smells
  • Extracted features: security score, technical debt, dependency risks
CI/CD & Monitoring
  • Jenkins / GitHub Actions / DataDog - Build status, deployment frequency
  • Extracted features: failure rate, rollback history, incident correlation
Decision Types

Typical software development decisions and their recommended allocation modes:

How Jira Fields Map to MCAT Dimensions
MCAT Dimension Jira/Ticketing Fields Example Calculation
Uncertainty (U) Story points, description clarity, acceptance criteria completeness U = 1 - (criteria_count / expected_criteria) * clarity_score
Novelty (N) Labels, components, similar resolved issues count N = 1 - min(similar_issues / 10, 1.0)
Value Conflict (W) Watchers count, comment threads, priority changes, linked blockers W = (watchers * 0.1) + (priority_changes * 0.2) + has_blockers
Data Quality Required fields filled, attachments, reproduction steps DQ = filled_fields / total_required_fields
Confidence Historical success rate for issue type, assignee track record C = type_success_rate * assignee_success_rate
Import a Scenario Disabled

Importing scenarios is temporarily disabled. A scenario is a JSON file (pure data — no code). View JSON schema ·