User Can Edit and Delete Existing Expenses

[Mari618]

This user story had two issues. Compare and consolidate or choose one.

User Story: As a user of the expense management application, I want to be able to edit or delete existing expenses, so that I can correct mistakes or remove expenses that are no longer relevant.

Acceptance Criteria:

1. Viewing Existing Expenses:

   • The user should be able to access a list of all existing expenses from the main expense management interface.
   • Each expense entry should have options to edit or delete.

2. Editing an Expense:

   • Access Edit Option: The user should be able to select an "Edit" option (e.g., button or icon) for any existing expense.
   • Modify Expense Details: The user should be able to update the following details for the expense:
     • Name of expense
     • Description
     • Category/Type of expense
     • Amount
     • Participant name
     • % Contribution of the participant
     • Receipt proof (upload a new file if needed)
   • Save Changes: After making modifications, the user should be able to save the changes.
   • Validation: The application should validate the edited data (e.g., ensuring the amount and percentage are correct) before saving.
   • Update Confirmation: The user should receive a notification or message indicating that the expense has been successfully updated.
   • Reflect Changes: The updated details should be immediately visible in the list of expenses.

3. Deleting an Expense:

   • Access Delete Option: The user should be able to select a "Delete" option (e.g., button or icon) for any existing expense.
   • Confirmation Prompt: The application should prompt the user with a confirmation dialog to confirm the deletion. This dialog should clearly indicate that deleting the expense is permanent and cannot be undone.
   • Remove Expense: Upon confirmation, the selected expense should be removed from the list immediately.
   • Post-Deletion Feedback: The user should receive a notification or message indicating that the expense has been successfully deleted.

4. Error Handling:

   • If editing or deleting an expense fails (e.g., due to a technical issue), the user should receive an error message explaining the issue and be given the option to retry or contact support.
   • The system should handle errors gracefully and maintain data integrity.

5. Permissions and Security:

   • Only users with appropriate permissions (e.g., the original creator of the expense or an admin) should be able to edit or delete expenses.
   • The application should ensure that any changes or deletions are logged and auditable for accountability.

Additional Notes:

• The user interface should be designed to make editing and deleting expenses intuitive and accessible.
• Clear and concise feedback is important to ensure users are aware of the actions they are taking and their consequences.

---

User Story: As a user of the expense management app, I want to be able to edit or delete existing expenses, so that I can correct or remove entries, while ensuring that the expense date remains unchanged.

Acceptance Criteria:

Editing an Expense:

Access Edit Option: The user can select an "Edit" option for any existing expense.
Modify Details: The user can update the following details:

• Name
• Description
• Category/Type
• Amount
• Participant name
• % Contribution
• Receipt proof
• Date Field: The date is displayed as read-only and cannot be changed.

Validation:

• Amount: Must be a positive number.
• % Contribution: Must be between 0 and 100, with increments of 10.
• Fields: All required fields (e.g., Name, Amount) must be filled in before saving.

Save Changes:

• The user can save changes, and the updated details (except the date) are immediately reflected.

Update Confirmation:

• The user receives a notification indicating the expense has been updated successfully.

Deleting an Expense:

• Access Delete Option: The user can select a "Delete" option for any existing expense.
• Confirmation Prompt: A confirmation dialog appears to confirm the deletion.
• Remove Expense: Upon confirmation, the expense is removed from the list, and the user receives a success message.

Date Immutability:

• The date is automatically set when the expense is added and cannot be modified during edits.

Error Handling:

• Editing Errors: If validation fails (e.g., invalid amount or percentage), the user receives clear error messages and instructions to correct the issues.
• Deletion Errors: If an error occurs during deletion, the user receives a clear error message and instructions to retry or contact support.

Additional Notes:

• The immutability of the date ensures accurate historical records, while allowing updates to other expense details.
• Validation ensures data integrity and provides clear feedback to the user.