[CONFIGURATION MANUAL // CONTROL-04]
Beam Settings Configuration
The Settings module allows you to fine-tune how beam interprets your Jira sprint data. These configurations directly impact your telemetry accuracy and determine the operational mode of the analysis engine.
1. DATA SOURCES & ESTIMATION
[SYS_VIEW // DATA_SOURCES]MUTABLE_SETTING
[X]
ENABLE TIME LOGGING ANALYSISESTIMATION METRICSTORY_POINTS
STORY POINTS CUSTOM FIELDcustomfield_10024
- // ENABLE TIME LOGGING ANALYSIS
- If enabled, beam extracts work logs directly from Jira tasks to compute raw sprint actuals. If disabled, the telemetry system relies solely on issue status transitions and sprint timeline markers.
- // ESTIMATION METRIC
- Defines the primary capacity metric for the sprint board. Options are strictly restricted to Hours, Story Points, or None.
- // STORY POINTS CUSTOM FIELD
- Identifies the unique custom field ID inside Atlassian Schema mapped for points extraction. This parameter is ignored if the estimation metric is set to hours or none.
2. OPERATIONAL MODES
beam dynamically adapts its calculations based on the combination of your configuration fields. The operational matrix below dictates the engine's behavior:
| Metric | Time Logging | Operational Mode | Behavior |
|---|---|---|---|
| Hours | Enabled | CLASSIC SCRUM | Aggregates actuals vs. estimates. |
| Story Points | Enabled | HYBRID AGILE | Tracks points vs. actuals in hours. |
| Story Points | Disabled | AGILE VELOCITY | Pure velocity tracking. |
| None | Enabled | SCRUMBAN | Tracks effort/hours without estimates. |
| None | Disabled | BASIC FLOW | Flow metrics via status transitions. |
3. THRESHOLD CONFIGURATION
[SYS_VIEW // VOLATILITY_THRESHOLD]MUTABLE_SETTING
SHADOW WORK WARNING (YELLOW)20%
SHADOW WORK CRITICAL (RED)40%
ADDED SCOPE LIMIT (RED)15%
Defines the sensitivity markers for triggering project alerts and status shifts inside your sprint reviews.
- Shadow Work Thresholds: Includes a Yellow warning state (warning threshold) and a Red critical state (high volatility alert) evaluated as a percentage of total sprint scope.
- Added Scope Thresholds: Controls the volume alert threshold for issue tickets injected into active sprints after board freeze.
4. SPRINT ADMINISTRATION
- // Grace Period (Minutes)
- Specifies the minutes buffer allowed directly following a sprint start where modifications and backlog additions are treated as part of the original commitment. Outside this timeline, changes translate immediately to Scope Creep.
- // Sprint End Buffer (Hours)
- Establishes a buffer period shortly before the sprint closes to eject incomplete issues from capacity equations, securing final metrics from late-stage manual updates.
💾 PERSISTENCE
Changes to the app parameters are saved instantly upon selecting the Save Settings control in the administrator pane. The system transitions the command button to a brief monochrome saved state for 3 seconds without full page refreshes.
SAVED ✓
SUPPORT MANUALNeed configuration help? Contact support@luxmetrics.com