User and Data should be deprovisioned

[db-ot]

Description

User Stories

• As an admin, I want to be able to delete a user account along with all related data and dependencies, so that the system stays clean and no orphaned data remains.

Value

• Prevents data clutter and ensures data consistency
• Improves system integrity by removing orphaned data

Acceptance Criteria

• shares (shares, links and spaces) and connected data gets deprovisioned
• • outgoing shares, links and space memberships (from perspective of the deleted user) get removed
• • incoming shares and space memberships (from perspective of the deleted user) don't get removed, but the UI must show "deleted user"
• INCOMPLETE LIST. find more acceptance criteria, especially regarding the personal space

Definition of ready

• [ ] Everybody needs to understand the value written in the user story
• [ ] Acceptance criteria have to be defined
• [ ] All dependencies of the user story need to be identified
• [ ] Feature should be seen from an end user perspective
• [ ] Story has to be estimated
• [ ] Story points need to be less than 20

Definition of done

• Functional requirements
  • [ ] Functionality described in the user story works
  • [ ] Acceptance criteria are fulfilled
• Quality
  • [ ] Code review happened
  • [ ] CI is green (that includes new and existing automated tests)
  • [ ] Critical code received unit tests by the developer
• Non-functional requirements
  • [ ] No sonar cloud issues
• Configuration changes
  • [ ] The next branch of the OpenCloud charts is compatible

[db-ot]

@tbsbdr / @kulmann can we discus in detail Acceptance Criteria > "Space Membership" is unclear and also the sense of incoming shares