search

Whysochong / pe

0 stars 0 forks source link

Project names are too restrictive #8

Open Whysochong opened 1 year ago

Whysochong commented 1 year ago

image.png

There might be 2 ongoing projects held by 2 different groups of people but the projects might have the same name, so it might make more sense to allow duplicate project names

nus-pe-bot commented 1 year ago

Team's Response

This is a duplicate as regardless of trying to add or edit a project name, if there is a duplicate is it not accepted. However we have mentioned this in our UG and also stated that adding a number behind as a unique identifier as an alternative so we reject this as a bug.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

User unable to add tasks or projects with the name

It is possible that as a user, I would want to add tasks of the same name for different days (eg. Finish Homework on 2022-11-11 and Finish Homework on 2022-11-12). Currently, the user must add a unique identifier to avoid duplicate detection, which may not be intuitive to users who need to perform the same tasks for multiple days in a row (hard to keep track of identifiers). It may be worthwhile to do input validation based on deadline as well.

[original: nus-cs2103-AY2223S1/pe-interim#3046] [original labels: type.FeatureFlaw severity.Medium]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

We decided to reject this issue because our task and project features were designed to not allow duplicates so it cannot be considered a bug. To add tasks with the same description, you can include an identifier at the back of the description as mentioned in our user guide.

image.png

There is also an alternative given for projects in the User Guide.

image.png

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)

Reason for disagreement: [replace this with your explanation]

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your explanation]

:question: Issue type

Team chose [type.FunctionalityBug] Originally [type.FeatureFlaw]

Reason for disagreement: [replace this with your explanation]

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: [replace this with your reason] image.png