Missing use case identification leads to hard to navigate among different use case

[jiasheng59]

In particular, reader can see create password is included as another use case but they have no clue where to navigate to get the this specific use case section.

[nus-se-script]

Team's Response

The use case for Create Password is immediately shown after Login use case description. Tester might have overlooked the use case which was shown immediately after Login use case description.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: It's not only that it happens in this particular use case. It applies to all other use cases in other part, I'm just taking this as an example to illustrate what issue I'm referring to

---