nus-pe-bot
commented
1 year ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Lack of support for tasks with longer names
What I did: add a todo event with a longer-length name.
As a user may need to enter a event with titles longer than expected, sufficient support should be in place to help facilitate this.
If such a limitation exists, it should be clearly communicated to the user, perhaps through a in app guide or UG.
This may render the user unable to see the full length of the event, and cannot retrieve desired info.
[original: nus-cs2103-AY2223S2/pe-interim#142] [original labels: severity.Medium type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
During normal usage, it is extremely unlikely that the user enters a title that is longer than 40 characters (which is being displayed in the screenshot provided). We provide additional description, location, tag fields to each task, where the user can enter more details if needed.
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 explanation]
## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
As pictured above, this may make indexing hard when the items do not start from 1 (eg, scrolling down the lists, where all of the events are long entries)