Purpose of listTasks and listInventory features?

[marcuslowhuiyu]

I am unclear as to the purpose of having the listTasks and listInventory features. Unlike suppliers, who have their own find feature, the list for both the inventory and tasks do not change as there is no equivalent find features for both of those lists. Therefore, it would be reasonable to conclude that both inventory and tasks would list down all their items always? In that case, would that not make listTasks and listInventory redundant? If the find features for inventory and tasks are implemented, it is not stated in the UG in the list of commands.

[soc-se-bot]

Team's Response

We have included all features we implemented as stated by the CS2103T textbook. The purpose of the listTask and listInventory feature is to list down all task and inventory respectively in the future if we have filter feature such as find. As stated in the textbook, future features are optional. Furthermore, listTask and listInventory are intuitive features is clearly explained in our user guide of what it does, hence this does not hinder user in using the application.

The 'Original' Bug

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

Unknown purpose of command

There is no need for these two commands since they have no commands such as find unlike suppliers.

---

_{[original: nus-cs2103-AY2223S1/pe-interim#553] [original labels: type.FeatureFlaw severity.Low]}

Their Response to the 'Original' Bug

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

This is to cater to future implementations that will alter inventory and tasklist.

We have included all features we implemented as stated by the CS2103T textbook. The purpose of the listTask and listInventory feature is to list down all task and inventory respectively in the future if we have filter feature such as find. As stated in the textbook, future features are optional. Furthermore, listTask and listInventory are intuitive features is clearly explained in our user guide of what it does, hence this does not hinder user in using the application.

Since it is catered to future implementations, I propose response NotInScope.

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]

---