Known issues
Track any production gaps here and tie them back to the audited onboarding spec so everyone knows which behavior is expected to be live today.
Note
Version 25.docx → Ripple Onboarding Guide — New Zealand Edition 2025 is the canonical contract for feature behavior. When you log an issue, reference the section that should deliver the promised experience (e.g., 4.1.5 for Jam tables, 4.1.6 for Notes, 4.3 for the context rail). This keeps the Known Issues list actionable and makes it easy for QA to verify fixes.
Issue log
| Issue | Impact | Workaround | Version 25 reference | Status / ETA |
|---|---|---|---|---|
| Describe issue | Who/what is affected | Temporary solution | Link to relevant section (e.g., §4.1.3) | Owner + next update date |
| Describe issue | Who/what is affected | Temporary solution | Link to relevant section (e.g., §4.3) | Owner + next update date |
| Describe issue | Who/what is affected | Temporary solution | Link to relevant section | Owner + next update date |
Add or remove columns to match your tracking needs.
Communication commitments
- Update channel → frequency → owner.
- Update channel → frequency → owner.
- Escalation guidance.
Callout for closure criteria
Note
Document how you confirm an issue is resolved (e.g. monitor metrics, validate with customers, post summary).