Team's Response

Refer to #2953

The 'Original' Bug

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

Lack of Word Wrapping

When entering any text parameters which are long, such as the dog name, tag and breed from the picture attached below, there is no functionality of 'word wrapping' which diminishes the user experience, and may even hinder the user from using the application.

---

_{[original: nus-cs2103-AY2021S2/pe-interim#2953] [original labels: severity.High type.FunctionalityBug]}

Their Response to the 'Original' Bug

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

A flaw that affects most users and causes major problems for users. i.e., makes the product almost unusable for most users.

First of all, the severity of High is too high for this bug, given that this is a non-typical user behaviour that we will elaborate below. This scenario is valid, but is much close to the definition of:

A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.

For names, I doubt that anyone will name their dogs with such a long name, just imagine having to call for your dog if you do :)

For breeds, all the breeds that I know of do not even take the half the screen width of the screenshot provided.

For tags, it doesn't make sense for tags to be that long either, tags are intended to be short and succinct, I doubt you see such long tags on social media right?

We can therefore conclude that these are all non-typical user behaviour that is rare and will not affect normal operations of the product. You might otherwise be thinking, why not limit the length of the input then, while that is a possible consideration, it is beyond the current discussion.

Items for the Tester to Verify

❓ Issue duplicate status

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

• I disagree

Reason for disagreement: This is not considered as a duplicate because of 2 reasons.

1. The dev team did not provide any justification for the bug I reported to 'prove conclusively that a bug is a duplicate'. Simply citing another issue did not justify anything. Furthermore, I disagree with the tester of the 'original' bug report when he combined 3 bugs into 1 bug and set it as a simple line wrapping issue. To me, this is a multiple bug report and more explainations can be found in point 2.
2. The main I reason I consider this as not a duplicate is because this bug can be fixed independently and it needs to be fixed independently for Name, Tag and Breed object. This means each of these three objects need to be changed so that objects with excessive long inputs can be prevented from being created and handled. One of the rationale is because Name, Tag and Breed may need to have different maximum length limit. For example, Name may allow longer input while Tag may allow shorter input. And this is exactly why I choose to report these as 3 individual bugs rather than 1 bug because each of these 3 bugs need to be fixed indenpendently. Thus, according to the definition of duplicate, these 3 bugs related to excessively long name, tag and breed are not considered as duplicates because they have to be fixed independently.

In conclusion, I feel that this is not considered as a duplicate because no convincing justification is provided for why these are duplicates when the original bug report is one which reports multiple bugs and each of these 3 bugs needs to be fixed independently.

On a side note, standing in the shoes of the developer team, I do feel it is unfair for them if all of these 3 bugs are considered as duplicates when there is a similar (but more general) bug report being posted. Thus, I decide to accept the bug related to tag as the duplicate of this identified original bug. However, the other 2 bugs I will keep my opinions unchanged as mentioned above.

❓ Issue severity

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

• I disagree

Reason for disagreement: I agree with the dev team that this is a rare circumstance. However, I disagree that this is unlikely to affect the normal operations. As explained in my bug report, not handling excessively long input for Name affects all of the three Entities in the application(Dog, Owner, and Programe), and all the commands related to the creation and deleting and viewing of these three entities (add dog, add owner and add programe and many more). This cannot be considered as "unlikely to affect normal operations" becuase these most important commands are not working as expected. Thus, in my opinion, this can should not be considered as Low.

On the other hand, I would also like to point out that there are some people with names longer than the default window length, such as

However, I still agree that these are a small group of users that may not be targeted at. But still, instead of assuming that this would not happen, a better approach is to handle it properly or mention it in the User Guide or Developer Guide about this issue and how it should be handled.

from pe.