Sprint Office
See your sprint as a living pixel-art office inside VS Code. Teammates gather around work areas based on ticket status, making blocked work and review queues easy to spot.
Start with the built-in demo
- Open VS Code 1.110 or later and a workspace.
- Run Sprint Office: Open from the Command Palette.
- Explore the fictional team, use the status filters, and click a teammate to inspect their tickets.
- Move the Sprint Replay slider to explore the illustrative demo timeline.
No Jira account or credentials are needed for Demo Mode.
Features
- Animated pixel office with working, review, blocked, idle, multitasking, and done states.
- Teammate details with primary ticket, ticket list, and notes.
- Status filters and team overview counts.
- Built-in fictional sample team for demos.
- Active Sprint mode to fetch a Jira board's current active sprint.
- Jira workflow transitions from ticket details when the connected account has permission.
- Sprint Replay controls with generated illustrative snapshots.
Sprint Office supports team coordination. Character position summarizes ticket state; it is not a measure of a person's productivity.
Connect Jira
This version supports PAT bearer authentication only. Use a Jira deployment that accepts a Personal Access Token in an Authorization: Bearer header and exposes the Jira Agile REST API. A standard Jira Cloud email/API-token Basic Auth flow and OAuth are not implemented.
- Run Sprint Office: Configure JIRA.
- Enter your Jira base URL, PAT, and numeric board ID.
- Run Sprint Office: Test JIRA Connection.
- Run Sprint Office: Sync Active Sprint, or switch to Active Sprint in the panel and sync.
Use HTTPS for your Jira URL. Your account must be able to view the board and active sprint. Jira permissions and workflow rules govern the transitions you can apply.
Credential storage and data handling
This release stores the Jira PAT in workspace settings, not VS Code SecretStorage. Do not commit, share, screenshot, or publish .vscode/settings.json containing the token. Use a disposable workspace for evaluation and remove the token when finished. The password-style input hides typing but does not encrypt settings storage.
Active Sprint mode sends authenticated requests to your configured Jira server to read sprint/issues/transitions and to apply a transition when you submit one. Demo Mode uses bundled fictional data. The recovered runtime contains no telemetry SDK or analytics endpoint; this statement does not describe VS Code's own telemetry behavior.
Commands
| Command |
Purpose |
| Sprint Office: Open |
Open the office panel |
| Sprint Office: Use Sample Data |
Return to the fictional demo team |
| Sprint Office: Reload Config |
Refresh the current view |
| Sprint Office: Configure JIRA |
Save Jira workspace settings |
| Sprint Office: Test JIRA Connection |
Check access to the configured board's active sprint |
| Sprint Office: Sync Active Sprint |
Fetch current sprint issues |
| Sprint Office: Toggle Mode |
Switch between Demo and Active Sprint |
| Sprint Office: Reset Config |
Return the panel to demo mode |
Limits in version 0.0.1
- Replay is illustrative. Earlier snapshots and time-in-state values are generated; this is not a Jira changelog, audit trail, or historical performance report.
- Demo Mode always uses the built-in sample team. The included JSON examples describe sample data, but this runtime does not load a custom workspace
sprint-office.json file.
- Sync is explicit; this is not a live push stream from Jira.
- Only bearer PAT authentication is implemented. Jira Cloud compatibility has not been validated.
- This is a desktop extension, not a browser-only VS Code extension.
Troubleshooting
If Jira fails, verify the base URL, bearer PAT support, board ID, account permissions, and presence of an active sprint. Test the connection again, then sync. The panel can fall back to fictional demo data after a Jira error; check its mode and warning before treating it as live work.
License
MIT. See LICENSE.md.