From dccd60031c48da9a71ad33cb0a7ff6366ff89457 Mon Sep 17 00:00:00 2001 From: Kawa Date: Mon, 30 Mar 2026 09:02:06 +0200 Subject: [PATCH] docs: define milestone v1.1 requirements (11 requirements) --- .planning/REQUIREMENTS.md | 68 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 .planning/REQUIREMENTS.md diff --git a/.planning/REQUIREMENTS.md b/.planning/REQUIREMENTS.md new file mode 100644 index 0000000..b6af4b7 --- /dev/null +++ b/.planning/REQUIREMENTS.md @@ -0,0 +1,68 @@ +# Requirements: Ready2Blob + +**Defined:** 2026-03-30 +**Core Value:** An IT pro can go from zero to a deployable rclone setup in minutes — without needing to know rclone's config syntax or PowerShell deployment conventions. + +## v1.1 Requirements + +### Tech Debt + +- [ ] **TECH-01**: User sees only the script output blocks matching their selected deployment targets (Intune and/or RMM) in ReviewStep +- [ ] **TECH-02**: User can navigate back from ReviewStep using an explicit Back button +- [ ] **TECH-03**: Backend list in BackendSelectionStep is automatically derived from BACKEND_REGISTRY keys (no hardcoded list) +- [ ] **TECH-04**: Dead `BackendFormValues` export is removed from `src/schemas/index.ts` +- [ ] **TECH-05**: BackendSelectionStep test suite runs without `act()` warnings + +### Backends + +- [ ] **BACK-01**: User can configure an OneDrive remote (with OAuth token paste input and guidance) +- [ ] **BACK-02**: User can configure an SFTP remote (host, user, password or key-based auth) +- [ ] **BACK-03**: User can configure a Google Cloud Storage remote +- [ ] **BACK-04**: User can configure a Backblaze B2 remote + +### Validation + +- [ ] **VALID-01**: User sees inline validation error when a field value violates backend-specific format rules (Azure account name: 3–24 lowercase alphanumeric; S3 region: valid format; etc.) + +### UX + +- [ ] **UX-01**: User can view a contextual tooltip on sensitive or complex fields (SAS token vs. access key, region codes, SFTP auth method, OneDrive token) + +## Future Requirements + +*(None identified — all backlog items are in scope for v1.1)* + +## Out of Scope + +| Feature | Reason | +|---------|--------| +| Multiple remotes in one config | Significant wizard UX complexity — defer to v2 | +| OAuth flow in browser (OneDrive) | Requires backend proxy; paste pre-obtained token instead | +| Test connection / credential validation | Requires backend proxy (CORS blocks direct cloud API calls) | +| RMM-named script variants | Generic SYSTEM-context script covers all RMM platforms | +| Save/load configurations | localStorage = credentials in browser storage = security risk | + +## Traceability + +| Requirement | Phase | Status | +|-------------|-------|--------| +| TECH-01 | — | Pending | +| TECH-02 | — | Pending | +| TECH-03 | — | Pending | +| TECH-04 | — | Pending | +| TECH-05 | — | Pending | +| BACK-01 | — | Pending | +| BACK-02 | — | Pending | +| BACK-03 | — | Pending | +| BACK-04 | — | Pending | +| VALID-01 | — | Pending | +| UX-01 | — | Pending | + +**Coverage:** +- v1.1 requirements: 11 total +- Mapped to phases: 0 +- Unmapped: 11 ⚠️ + +--- +*Requirements defined: 2026-03-30* +*Last updated: 2026-03-30 after initial definition*