CivicDataLab / CivicDataLab/DataSpaceFrontend
[Bug] 'All Changes Saved' autosave indicator shows even when all required fields are empty
Open
@Abhishekfm is already working on this.
Since Jun 22, 2026.
bug
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 19
Description
Summary
The model editor header always displays "All Changes Saved" regardless of whether any required fields have been populated. The autosave indicator tracks the existence of the draft record, not the completeness or validity of its content.
Impact
- Creates a false sense of security — users who fill nothing see "All Changes Saved" and may think their model is ready
- The indicator fires for every keystroke via GraphQL mutations, but never communicates that the model is incomplete
- Contradicts the Publish step which correctly shows all missing required fields
Observed Behaviour
- New model created (empty)
- Editor header immediately shows "All Changes Saved"
- All required fields (Sectors, Tags, Languages, etc.) remain empty
- "All Changes Saved" continues to show throughout the session
Fix Recommendation
Change the indicator to differentiate states:
- ✅ "All Changes Saved" — when all required fields are filled
- ⚠️ "Draft saved — metadata incomplete" — when required fields are missing
- 🔄 "Saving..." — during active save
Environment
- URL:
https://dev.civicdataspace.in/dashboard/organization/civicdatalab/aimodels/edit/{id}/details - Discovered: 2026-06-22 via QA audit
- Report ref: CDS-003
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.