IssueFour Refactoring
Explanation
- Original Issue (
[IssueFour](https://git.cardiff.ac.uk/c2038058/ase_y2s1_cp_g4/-/issues/4)) gained too complex to carry on with and no longer functions as an issue or code feature - Issue has now been remade, and all code removed and refactored to work better with the new systems in place
Acceptance Criteria
- Josh
- All non-functioning and old code removed
- Create a form for user to input information
- Send form data to controller
- Salt + hash password
- Store information in database via JPA
- Make it so user cant use an email that has already been used
- Ethan
- Allow user to pick up to 3 to set as favourite
- Send list of tags to server
- Save list of favourite tags to database
Tracking Data
| Stage | Date |
|---|---|
| Entered Open at | 2021-11-26 12:14:00 |
| Entered Ready at | 2021-11-26 12:18:00 |
| Entered Dev at | 2021-11-26 12:18:00 |
| Entered Test at | 2021-11-30 10:32:00 |
| Entered Done at | 2021-12-02 12:46:00 |
| Entered Closed at | 2021-12-02 12:46:00 |
Definition of Ready
- Issue is populated with relevant Acceptance Criteria
- Issue name meets the format “As a I want so that ”
- Issue is not dependant on any, non-closed, issue
- Issue appropriately weighted based on team opinions and planning poker session(s)
- If issue has a corresponding UI element, it has a “UI Plan” created before development begins
- If Issue has a corresponding DB element, it has an ER Diagram created with corresponding changes before development begins
- All above points verified by a member of the team external to the main developer(s) of the issue
Definition of Done
- At least one automated test per major feature created during the process of the issue
- All acceptance criteria complete and met
- All relevant tests pass
- Appropriate Javadoc present throughout
- All above points verified by a member of the team external to the main developer(s) of the issue