Open WuJinhan1 opened 1 week ago
WuJinhan1
commented
1 week ago 
It says on the UG that it automatically updates to unpaid for the first of each month or the first of three months etc... However, when I changed my date to these and refresh the detail view, it doesn't update to unpaid. I know that changing the date manually works because when I change my date for the birthday feature, it worked.
nus-se-bot
commented
1 week ago Tested this issue ourselves but unable to find any issue with the result. Could possibly be that tester did not relaunch the app to allow for the reset to take place.
Team chose [response.CannotReproduce]
Reason for disagreement: After looking through the UG, I could not find any place that said you would need to relaunch the app for the reset to take place. The only refresh that I was made aware of is this, which states that you would need to double-click on the same client for the refresh to take place in the detail view. Which I tried and did not work during the pe. So I would change the issue to a documentation bug as it was not specified in the UG.
However, after testing by relaunching the app for the reset to take place, I found another critical bug. Any data input on the first day of the months specified in the user guide fails to save, which is a serious issue and qualifies as a high-severity functionality bug. This is because it is set under the pretext that the feature is intended to work, but instead, it removes payment data for clients who have already been marked as paid when updated on these specific dates. This could jeopardize the financial advisor and their client's relationship, as one party may believe a payment has been made while the other sees it as unpaid due to the app's automatic update.
Here is an example of the bug. I have set the date to December 1 and updated the first client with a one-month frequency. However, when relaunching the app later on the same day, the status is set to not paid and the policy renewal frequency has been set to 0. I have not changed anything during this time and have just relaunched the app.
