[UI] Assignment gets truncated when window is resized

[anselmlong]

Overview:

The word Assignment and the entire field gets truncated when the window is resized smaller.

Environment:

Processor: 13th Gen Intel(R) Core(TM) i5-13500H, 2600 Mhz, 12 Core(s), 16 Logical Processor(s) Operating System: Microsoft Windows 11 Home Version 10.0.22631 Build 22631 App Version: v1.6

Steps to Reproduce:

1. Add any person to the list.
2. Resize the window until the word "Assignment" becomes "..."

Expected Result:

Assignment should not be truncated.

Actual Result:

Assignment is truncated.

Screenshots/Logs (if applicable):

Frequency:

Always.

[soc-se-bot]

Team's Response

Firstly, the assignments themselves do not disappear upon resizing, only the assignment label disappears. So we believe that the user can still see and interact with each assignment meaningfully. Hence, we believe this is a cosmetic bug.

Secondly, we believe that users who resize the windows to a smaller size would expect to see lesser details (i.e. a truncated version of the application). For any application, making it too small would impede its functionality and readability. Hence, we do not think this is a priority to implement in v1.6.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: Your product in v1.6 should be usable, and the UI is part of the client-facing product. Hence, UI bugs should be in the scope of this iteration. Furthermore, the other fields do not truncate, and only the Assignment field does so. Furthermore, it's not that there are purely lesser details, but the field is truncated while the others are not - showing that there is a bug in the UI functionality.

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** > severity.VeryLow : A flaw that is purely cosmetic and does not affect usage e.g., a typo/spacing/layout/color/font issues in the docs or the UI that doesn't affect usage. Only cosmetic problems should have this label. I have to disagree with this rating, as this bug does affect usage, where the user cannot see the label:  However, I do agree my initial rating of Medium may be too high. I propose to downgrade it to `severity.Low`.

---