search

chloeelim / pe

0 stars 0 forks source link

UG: Interface explanation #8

Open chloeelim opened 1 year ago

chloeelim commented 1 year ago

UG is lacking explanation on the interface (person card); to the user, it is not very clear what the differently colored tags in the person card mean because there is no such explanation in the UG. It would be good to include explanation on this so the user doesn't have to go test it out using commands to find out.

soc-se-bot commented 1 year ago

Team's Response

image.png

image.png

Thank you for your suggestion. Our target users are Minecraft players with experience, and they should be able to recognize game types, Minecraft servers and social media handles with ease.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: While I do understand that the target users of the app are Minecraft players, I think the team should also consider the case that it is in fact possible that there are overlaps between possible tag names and possible game types.

I'll use the explanations in the team's UG for illustration (attached below).

  1. Notice that both tag names and game modes "can be anything".
  2. Note that tags are "used to provide additional information about your friend". (which I assume the user can use to describe their friend [adjectives]: which do corroborate with the screenshots used in the UG)
  3. However, as the team has in fact illustrated in their example below, a possible game mode is creative, which happens to be something you can also use to describe a friend and thus, is a very valid tagname too!
  4. The user now can't tell whether colored-tag with a label creative represents a gamemode or a tag name; the only way he can find out is to try executing some commands to test things out (or hope he has other friends with gamemodes/ tags that allow him to differentiate between the 2 clearly) since there is nothing in the UG he can refer to :(

[same thing can happen between server names and social handle names [it was even trendy for a while to have a .com behind your IG handle so this isn't really that far-fetched a possibility] though I'll concede that this case is less likely (but still entirely possible)]

Unfortunately, I think the team failed to consider such valid cases when providing their justification when rejecting this bug entirely. Making the assumption that their users will be able recognize game types, Minecraft servers and social media handles with ease might be too big of an assumption to make.

Eg: This is a valid person I can add to the application- would the user be able to tell which coloured tags correspond to tag names, game types, server names and social media handles?

Screenshot 2022-11-16 at 1.45.31 AM.png

As such, this is a hindrance to the user and should be documented in the UG, rather than being rejected entirely. Since this bug requires a fix by editing the UG, this should be considered a DocumentationBug.

Screenshot 2022-11-16 at 1.22.20 AM.png

:question: Issue severity

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

Reason for disagreement: This is not a purely cosmetic issue and thus, should not have the label severity.VeryLow.

I think this bug fits the label severity.Medium instead, which is:

A flaw that causes occasional inconvenience to some users but they can continue to use the product.

  1. Occasional inconvenience to some users

✅ Occassional: True, using creative as a game mode probably a very commonly used game mode tag (the team even used it as an example in the snippet of the UG above in the issue response response); and creative is also likely to be commonly used to describe friends (especially in a creative game like Minecraft)

✅ Inconvenience: In this cases, the user might not be able to tell between the 2 tags and there is no way to find out by referring to the UG since the UG does not provide an explanation for the differently colored tags. The user has to try out commands, or refer to other person entries to figure this out which definitely is a source of inconvenience

  1. They can continue to use the product

✅ Of course users can continue to use the product, no issues here, just inconvenienced caused!

Since the bug fulfills the 2 criteria to be considered a severity.Medium bug, and definitely is not a purely cosmetic issue, I'd (respectfully) disagree with the team's decision to downgrade this bug report to a severity.VeryLow issue and stand by my original judgement.