soc-pe-bot
commented
10 months ago Team's Response
You are right about the patch portion of the version number! Thanks for catching that. However, we do not think that users will usually refer to the terminal. Also, we think it will not affect the usage of the application, hence for it to cause a lot of confusion to the users due to the difference in the patch version number might be a little far-fetched.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: I must respectfully disagree with the assessment that having an incorrect version number is unlikely to cause confusion and that its impact on user experience is negligible. The version number of an application serves as a crucial reference point for users for several reasons:
Software Identification: Users often refer to the version number to ensure they are using or referencing the correct iteration of the software, especially when troubleshooting issues or seeking help. A discrepancy in the version number could lead users to question whether they have the latest update, potentially affecting their trust in the application's maintenance and support structure.
Impact on User Decisions: An incorrect version number, especially if it indicates an 'early access' or beta stage, may influence user decisions regarding the use or purchase of the application. Users may hesitate to use an application that appears to be in a pre-release or developmental stage due to concerns about stability and feature completeness (users might think the version they wanted v1.4.0 is not out yet and continue to wait).
Importance for Technical Support: Accurate version numbers are essential when users seek technical support or when reporting bugs. Incorrect versioning can lead to miscommunication with support teams and hinder the effective resolution of issues.
Documentation and Training Materials: Inaccurate version numbers can affect the relevance of training materials, user guides, and tutorials, which might be version-specific. Users trying to follow these materials could encounter discrepancies if the version number in the application does not match that in the instructional content.
Therefore, given the potential for user confusion and the implications for user support and documentation, the incorrect version number should be viewed as more than a trivial issue. It directly impacts the usability and perceived reliability of the application. Consequently, this issue merits a higher severity rating than suggested and should be promptly addressed to align with best practices in software versioning and release management.
if im not wrong its version is suppose to be v1.4.0 and not early access.
Having the wrong version can cause a alot of confusion to users when they are trying to get the latest version of your application