soc-pe-bot
commented
2 months ago Team's Response
We have addressed this concern in our FAQ in the user guide.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
The new command allows users to be able to add items to the inventory, however there are checks in place to prevent items with the same name to be added. However, this can prevent items of the same type but have different expiry dates to be added. Supermarket items do not necessarily have only one expiry date, items can be restocked in batches, with each batch of item having multiple expiry dates.
As a supermarket stock manager, if I have many items that are perishable(have expiry dates), I might want to be able to have items of the same type but have different expiry date. The work around to this issues is to have different names for items of the same type but different expiry date, which may not be very intuitive and it introduces the repetitive work of having to specify a expiry date in the name and in the "expiry date" field. It can also result in the inventory filling up really quickly if there are may batches but not many types of items.
One possible work around is to not only check items names for duplicates but also expiry dates.
Severity is set to medium as supermarket may have many perishable items that requires managers to indicate different expiry dates for the same types of items and not having a feature which supports this may be inconvenient to the user.