Adds implementation plan for CSV import closes #287 #314
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
UX research
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: local-it/mitgliederverwaltung#314
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/287_plan_csv_import"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the implemented changes
The changes were:
What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
Looks like a good concept. I would prioritize the custom filed import/export maybe a bit higher, because not being able to import/export the custom fields could lead to unexpected data loss. But only if it's not too much extra effort.
@ -0,0 +51,4 @@### Out of Scope (v1)**Deferred to Future Versions:**- ❌ Upsert/update existing membersWe could export/import the member UUID this way we could uniquely identify the members and update their records. I think this way an upsert shouldn't be much extra effort.
I like the idea but due to ressources I would for now keep that as "future idea" because I don't see that much a use case for that..Is that fine for you?
828e09dce1to00ff2fa195