Settings Page

[melanie-adler]

Value Proposition

As a user I want to have access to a dedicated settings page In order to customize and manage my app preferences and personal information.

Description

Acceptance Criteria

• The Settings page is accessible from any page via a settings icon placed on the top right corner.
• When adding or editing a transaction the icon for the settings page should appear next to the category where the user can click the icon and go to settings page.
• The Settings page shows every existing category.
• A new category can be added via an input field at the bottom of the category list.
• A Back button should be available on the Settings page, allowing users to exit the settings and return to their last visited page or homepage.
• A confirmation message appears after saving a new category, indicating that the addition was successful.

  Tasks

• [x] Create feature branch feature/settings-page.
• [x] Design the settings page layout with headers for the category section.
• [x] Create an input field with a '+ Add new category' placeholder.
• [x] Implement validation to ensure the category name is unique.
• [x] Ensure that the new category is added to the list and reflects immediately in the dropdown.
• [x] Ensure that the dropdown in the transaction form is updated immediately after adding categories.

[ahohnsen]

Hi there!

I have a few questions and suggestions regarding your user story:

Description

Please take note of the resolution of your wireframes - they are currently difficult to read. 🔍

Acceptance Criteria

The Settings page is accessible from any page via a settings icon.

It would help to specify where this icon is located. If I’m interpreting the wireframes correctly, it appears to be in the top right corner on most pages, including in the form to add a new transaction. However, in the next acceptance criterion, you write:

When adding or editing a transaction, the icon for the settings page should not be clickable.

I’m wondering why the settings icon would appear in the form if it’s not meant to be clickable during the add/edit process. This seems inconsistent, or possibly the wireframes and acceptance criteria don’t fully align. Of course, this might also be due to the low resolution of the wireframes, which makes it difficult to interpret the details accurately.

You mention that users can add new categories on the settings page. But can categories also be edited and deleted there? I ask because your wireframe already includes icons for these actions, but these functions aren’t mentioned in the acceptance criteria. Here are three possibilities:

1. If these functionalities have already been implemented in a previous user story, you should still note here that categories can be edited and deleted on the settings page.
2. If these functionalities are planned for a future user story, the wireframe should not yet include these icons.
3. If you intend to implement these functionalities in this user story as well, I’d advise against it since it would make the user story too large.

Additionally, your acceptance criteria should explain how the user can exit the settings page. In your wireframes, it looks like there’s a back button. Please include this in the acceptance criteria, specifying where the back button will take the user—e.g., to the homepage or the last visited page.