Vinodjayakumar124 / pe

0 stars 0 forks source link

Unable to remove optional deadline for project #4

Open Vinodjayakumar124 opened 1 year ago

Vinodjayakumar124 commented 1 year ago

Able to create a project without a date as deadline is optional. However, after adding a deadline through the project -e (edit) command, I am unable to remove a date from the project.

If date is an optional field, we should be allowed to remove the deadline after adding it.

To replicate the issue: project -a n/Test

image.png

project -e p/9 d/2022-12-12

image.png

However, unable to add an empty deadline or remove the deadline any other method.

image.png

nus-pe-bot commented 1 year ago

Team's Response

Thanks for the bug report! We acknowledge that having a method to remove deadlines would be a great improvement to existing features however it is not within the scope of v1.4 features. A user at this moment can delete the project and re-add it with no deadline if needed. Furthermore, many projects are expected to have a deadline, and also after adding a deadline, it is not usual that a user would want to remove the deadline - it is more likely that they would want to extend or shorten the deadline. Hence, the report should not be of 'Medium' severity but rather 'Low' severity.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: The number of lines of code required to allow for the deadlines edited to remain optional based on their codebase (i.e allowing a null field) is within 5 lines that is placed within an if-else block that checks for the an empty value that can be validated and allows the current datetime to be replaced with null.

As per the instructions from the CS2103 website,

image.png

Therefore, due to the minimal amount of effort required to allow the deadlines edited to remain optional, I believe that this issue is still in scope. Furthermore, it allows for more consistency between the 'add command' and 'edit command', whereby the deadline can always remain optional.


:question: Issue severity

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

Reason for disagreement: [replace this with your explanation]