search

jyztintan / pe

0 stars 0 forks source link

Unable to see full long remarks #17

Open jyztintan opened 2 months ago

jyztintan commented 2 months ago

When inputting very long remarks for internship entry, users are unable to see the full long entry.

In the normal app view

image.png

In the detailed app view

image.png

severity.Medium - Since the application allows users to input long inputs for remarks with no character limit, it should also allow them to retrieve these potentially important information. This could frustrate and inconvenience users.

soc-pe-bot commented 2 months ago

Team's Response

It's a duplicate, because both involves the UI component truncating the values instead of expanding outwards.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Long emails not shown in the Detailed Internship View

image.png

image.png Implemented well in the main window, but in the Detailed Internship view window, the full email is not shown even though it supposed to be more detailed than the main view.

[original: nus-cs2103-AY2324S2/pe-interim#5281] [original labels: type.FeatureFlaw severity.VeryLow]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No details provided by team.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: In the "Original bug", the POC's full email is still visible when switching to the normal app view, as a workaround to view the long email input. However, this is not the case for remarks as specified in my bug report. Users are left unable to retrieve their full remarks in both the normal app view and the detailed app view. Hence, I feel that this bug report should be of a higher severity than the "original bug" as it poses a more significant issue (with no workaround) to users.

## :question: Issue type Team chose [`type.FunctionalityBug`] Originally [`type.FeatureFlaw`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** The team has responded with a change in the severity to "veryLow", and classified my bug report #17 as a duplicate of the original bug but with no explanation provided to address the change in severity. I would like to present additional considerations that suggest that the severity of bug should definitely not be "VeryLow" which is reserved only for purely cosmetic issues, and "UI that doesn't affect usage". The team's classification of "severity.veryLow" overlooks the functional aspect of the bug. Users who input lengthy remarks expect to retrieve and review these details later, possibly for important decision-making or record-keeping. When these inputs are not fully visible, it affects more than just the aesthetic appeal since it directly impedes its functionality, as the app does not fulfill its intended use of displaying entered data. In the "Original bug", the POC's full email is still visible when switching to the normal app view, as a workaround to the long email input. However, this is not the case for remarks as specified in my bug report. Users are hopelessly unable to retrieve their **full remarks** in both the normal app view **and** the detailed app view. I believe it aligns more closely with the "Medium" severity definition, as it "causes occasional inconvenience to users" who need to access these entries in full. Furthermore, because this bug remains undocumented and users receive no prior warnings about it, they are likely unaware of the risk of crucial data loss (which is usually the case for long remarks). This inability to view complete information disrupts the user experience significantly, especially when the data is crucial . I had thoughtfully considered the following in determining this issue's severity: 1. Potential for Significant Inconvenience: This bug could significantly inconvenience users, in scenarios where access to necessary information is impeded, affecting their ability to perform essential activities. 2. Undocumented Nature of the Bug: The lack of documentation exacerbates the problem, leaving users unprepared for and unaware of the potential for data loss, thereby increasing the risk of impact on their operations. 3. Frequency of Occurrence: The frequency in which users might encounter this issue when using the app for its intended purpose seems more than rare, especially since this issue appears to affect multiple fields suggests that its impact is widespread and not isolated to rare cases 4. The issue lies with the UI but it hinders usage, and should not be underplayed as a mere cosmetic flaw. I believe that reevaluating the severity to "Medium" but definitely minimally a "Low" would better align with the impact it has on user functionality and experience.