Delete DI on Adorsys Lissi Blockchain

[TamaraHoock]

User story

1. As a {HR-Employee}
2. I want / need {to be able to delete an existing DI}
3. So that {existing DIs are eliminated}

Acceptance criteria

• Create a button designed with a "bucket" icon on the DI overview table on the right side in each column, to allow the deletion of one DI based on the selected column
• Moving cursor above bucket should activate a description "Delete DI"
• Clicking on bucket should activate a pop-up window:
  "Delete DI
  Are you sure you want to the delete the DI for {DI-name}?"
  • pop-up window should have a tick box "Yes, I want to delete the DI"
  • Pop-up window needs a delete button, that is colored grey (not yet activated) and can't be clicked on directly. Delete button can only be activated (colored in red), once the tick box is filed out.
  • Pop-up window needs a cancel button, that cancels this process and leads user back to DI overview table
• feedback on success/error is displayed in frontend
• pop-up window to inform hr-employee that DI was successfully deleted "The DI {DI-Name} was successfully deleted"
• DI is fully deleted in Lissi and our database

Definition of done (DoD)

• code peer-reviewed (by at least one team member)
• acceptance criteria met
• integrated into a clean build
• documentation updated
• code is well-formatted (according to our norms) and structure
• Code supports all functions/cases and all responses defined in the API
• no severe bugs during main functionalities (program should not stop executing due to these bugs, e.g. runtime exception in Docker)
• Bill of Materials updated if necessary
• 70% of the tests pass
• important functions shall be tested
• code has been deployed via Docker to the server

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release

[jackDS008]

Discussion (Sprint Review 22.06.2022)

• Should the user be deleted when the DI gets deleted?
• Should the e-mail be unique or should it be possible to create more than one DI with the same e-mail?