search

Austintjh19 / pe

0 stars 0 forks source link

When entering long address. Details may be cut off. #7

Open Austintjh19 opened 1 month ago

Austintjh19 commented 1 month ago

image.png

When entering long address. Details may be cut off, when screen is resized smaller.

nus-pe-script commented 3 weeks ago

Team's Response

As for sample startup 2 and 3, the usual address should be available to see in CapitalConnect without being truncated. In cases of a super long address, although it might be a potential problem, we believe it is very rare. Also, given that your screen is resized even smaller, CapitalConnect should be able to display this information better under a normal screen size.

The 'Original' Bug

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

Key Employees and Notes Container are not Displayable when Screen Width is resized Smaller

image.png

Unable to view Key Employees and Notes when application is resized smaller. Might cause some incovenience to users. Maybe consider setting a minimum width for the application.

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

Their Response to the 'Original' Bug

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

In the project constraints given for TP, the application should be usable for resolutions 1280x720 and higher. We believe that this bug is not in scope as the width size used to achieve this bug is outside of regular user behaviour outlined in the project scope.

Screenshot 2024-04-20 at 10.39.33 PM.png

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: [replace this with your explanation]

## :question: Issue response Team chose [`response.NotInScope`] - [x] I disagree **Reason for disagreement:** This constraint on screen resolution is not provided on the UG. As a tester that potentially does not know anything about the TP constraints, this is a flaw.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.VeryLow`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]