nus-pe-bot
commented
4 years ago Team's Response
The whole purpose of UniSave to to help you track your expenses that are ALREADY SEPNT. It is clearly stated in our user guide that we only support REAL expenses which DOES NOT INCLUDE PLANNED FUTURE EXPENSE. Moreover, it should be easy and intuitive enough for users to understand that we do not support future dates from the user guide.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: From the UG of UniSave, the purpose stated in their explaination is not consistent with the content in their UG.
In their explanation, they stated that it is written in their UG that they only support real expenses, which do not include planned future expense.
However, in their actual UG (see SS below), there is no mention about not allowing planned future expense. Moreever, in their main target audience which is University students, they cited expenses such as tuition fees, housing fees as examples, both of which are expenses that are often forecasted into the future.
For example, if a student were to budget 3k for each month, the student would know that in the middle of the coming month, he would have to pay upcoming housing fees, thus he should be able to forecast expenses to reflect an accurate budget.
Therefore it is not obvious that future dates are not supported from the user guide.
The error message states that a DATE can be entered as long as it is a single number, lesser than LARGEST_DAY_AGO.
Thus, if i want to add an expense which i forecast to spend tomorrow, I would add t/-1, however, the command turns out to be rejected even though it is a single number and lesser than LARGEST_DAY_AGO
Furthermore, it only states that you are unable to add a date in the future when entering in date format, but not in number format.