nus-se-script
commented
4 days ago [IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Team's Response
As quoted from the course website: "In general, a flaw (e.g., a missing feature, a suboptimal design of a feature, a known bug) can be considered NotInScope if rectifying it is less important than the work that has been done already (because it is fine to delay lower priority work until future iterations)"
This is considered a missing feature and adding it is not very important and low priority as we feel that the other features would be more important as users can already delete and add the internship application. We plan to delay this lower-priority work until future iterations
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Lack of edit feature.
We are all no strangers to making mistakes. I believe adding an edit feature to the product would be useful. For instance if a user had typed in an entry for a job but made a slight spelling error in the company name, he would have to completely delete the entry and retype it. This can be quite frustrating for a user who is balancing many different things such as school, assignments, lectures and exams.
Product can be better improved with an edit feature.
[original: nus-cs2103-AY2425S1/pe-interim#2803] [original labels: severity.Medium type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
As quoted from the course website: "In general, a flaw (e.g., a missing feature, a suboptimal design of a feature, a known bug) can be considered NotInScope if rectifying it is less important than the work that has been done already (because it is fine to delay lower priority work until future iterations)"
This is considered a missing feature and adding it is not very important and low priority as we feel that the other features would be more important as users can already delete and add the internship application. We plan to delay this lower-priority work until future iterations
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]
There is no command for the user to edit their entries. Instead, the User has to delete and add their entry again which may be frustrating to type in if it is only a small error to change.