soc-pe-bot
commented
1 week ago Team's Response
Thank you for bringing this issue up to us. The issue prevents users from modifying previously entered date value, disrupting workflow where dates needs to be adjusted.
Our team acknowledges the disruption to workflow pertaining to the update of "Date" field data type. However, in the nature of "update" command, users can still fall back on "deleting the record and re-entering it" in the event of this situation. Although this require addition steps, it ensure users can still achieve the changes desired.
As defined in the PE guide "severity.Medium: A flaw that causes occasional inconvenience to some users, but they can continue to use the product." Our team feels this would be an issue that fits the severity of "Medium" due to its occasional inconvenience it causes for users but they can still go through the means provided above of achieving the changes required.
For "severity.High": A flaw that affects most users and causes major problems for users. i.e., only problems that make the product almost unusable for most users should have this label. We think that the product is very much still usable as there are no catastrophic events like crashing or loss of data. Hence, the issue does not meet the threshold of "High" severity.
With that said, we apologise for the inconvenience caused and will ensure that this is rectified in the next iteration of Inventra!
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Medium]
Originally [severity.High]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
When trying to update value in a field of type date, it ends in error message of Invalid Input. A user must be able to update a date that was earlier entered.