Latest ver jar file not updateed

[Stella1585]

Links leads to v2.0 release.

[soc-se-bot]

Team's Response

We acknowledge that there was an oversight in failing to update the jar file, however users are still able to easily access the v2.1 by visiting the Releases page, and from the DG it is apparent that our current latest version is v2.1. Users are still able to access the latest issue, and we feel that the the severity should be "Low".

From the previously mentioned reasons, our team believes that the severity should not be "High" because the latest jar file is still accessible, and it does not make the product completely unusable.

Items for the Tester to Verify

❓ Issue severity

Team chose [severity.Low]
Originally [severity.High]

• I disagree

Reason for disagreement: Based on ur description

i think it should be severity.Medium instead when compared to the description of bug labels given.

This is because i do not think that this will be a rare situation as most people will follow the instruction given in the UG/DG/Readme to start using the app. Placing the v2.0 link might lead them to think that there might be a typo and v2.1 should be v2.0 instead. If not almost everyone who access the app through the link will have to navigate to v2.1 release themselves which definitely causes occasional inconvenience.

---