Here we are listing down all the user stories which will go into iteration 1. Please note that the word “Feedback” and “Posts” are used interchangeably here.
User Story 1: As An Admin I should be able to create feedback boards from team setting screen.
Summary:
An admin can create feedback board from the team settings screen. Feedback boards are nothing but a collections of “Feedbacks”. They can be considered similar to “Categories”. For example, you can create a feedback board and give it a name “Bug fixes” and all the feedbacks which can be categorised as bugs can come under this board. Similarly, if you have mobile app and you want to see all mobile app issues in one group, you can create a feedback board titled “Mobile App” and user can report issues regarding mobile app under this category.
Acceptance Criteria
- Admin should be able to go to Team Settings and Add Feedback Board there.
- It is just name (string, text) and there is nothing much to it.
- Admin should be able to edit the name if he wants to. It has to be inline editing
- Admin should be able to delete the feedback board.
- There will always be a “default” feedback board. This will be named as “Feature Requests”. It can not be deleted but it's name can be changed. Each team will have this one default board.
- This default board will be also selected as default board on public url when there are more than one boards.
- We DO NOT need option to change default board as of now and user can not make some other board as a default board.
- Each team (or product) have it's own set of Feedback board and therefore this comes under team settings but not account settings.
Validations and errors:
- When adding a new feedback board, name can not be empty string.
- Under a project, name of broads have to be unique.
- When deleting a board, only that board can be deleted which has no feedback added under it, otherwise show error alert that board can not be deleted since there are feedbacks under it.