fjborquez / katara

Frontend for Avatar project
0 stars 0 forks source link

Enable | Disable house by person #16

Closed Norbbs closed 5 months ago

Norbbs commented 6 months ago

As a Data Owner I want to enable or disable user data from the system So that I can only keep the relevant data

Definition Of Ready (DoR)

Definition Observations
  • - [x]
The story meet the INVEST and SMART criteria
  • - [x]
Dependencies identified and resolved
  • - [x]
Written acceptance criteria with test scenarios, understood by the team and agreed upon
  • - [x]
The user story was understood and agreed upon in a refinement session with the dev team
  • - [x]
The team has an idea of how to make the demonstration of the finished story

Scope

  1. Select user from users data table information and confirm the action DELETE.

Out of scope

  1. create, update and other non-delete processes.
  2. not including profile update.
  3. not including login.

Acceptance Criteria

AC GIVEN WHEN THEN
  • - [ ]
1 Enable house from data table A table with information about houses disable option is available and clicked by user a frontend structure will appear to confirm or cancel the action
  • - [ ]
2 Disable house from data table A table with information about houses aneble option is available and clicked by user a frontend structure will appear to confirm or cancel the action
  • - [ ]
3 Confirm house enabling a frontend structure for confirm the action confirm button is clicked the house information selected must be change from disable to enable and refresh the table
  • - [ ]
4 Confirm house disabling a frontend structure for confirm the action confirm button is clicked the house information selected must be change from enable to disable and refresh the table
  • - [ ]
5 Cancel user data enable/disable a frontend structure for confirm the action Cancel button is clicked the structure must disappear and keep the user information.

Definition of Done (DoD)

Definition Result
  • - [x]
All acceptance criteria have been met
  • - [ ]
No significant or critical defects
  • - [ ]
Deskcheck ceremony has been made
  • - [ ]
Keep minimum test coverage of 80% over the necessary code and components
  • - [ ]
Technical documentation published
  • - [ ]
Spike, PoC or benchmarks findings documented