Open nidhi-nayak opened 6 months ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Thank you for identifying this and I appreciate your diligence in catching this discrepancy.
While the plural form of the command deviates from the documented singular version, it does not impede the functionality or operation of the application, as the command still executes as intended without causing any errors or failures.
The User Guide and the the menu
command in the app provide the correct command format, ensuring that users have access to the proper usage information. The bug appears under very rare circumstances and does not result in any significant inconvenience to users. It should be seen as a minor discrepancy rather than a functional flaw that is of High Severity.
Given the definitions behind the severity labels, a Low severity would be more fitting, considering that it is a flaw unlikely to affect normal operations and occurs only in rare situations, causing minimal inconvenience. Therefore, the severity of this issue should be adjusted to accurately reflect its minimal impact on the application's usage from a severity.High to severity.Low
Team chose [severity.Low
]
Originally [severity.High
]
Reason for disagreement: [replace this with your reason]
The command described in the app and the UG is
edit expense
singular, butedit expenses
is a valid command and works:same with the command 'edit expenseyyyy'