Can include the definition of the tags in the glossary

[SahanaAvantika]

Could define Candidate and Rejected, and reiterate the assumptions and the constraints that come together with the tags maybe? Like for rejected how they will not be allowed to schedule interviews

[soc-pe-bot]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Though extra clarity can be helpful, the glossary is meant to explain to users more technical, tech-related terms, and the meaning of Offeredand Rejectedshould be sufficiently self-explanatory for users. The user behavior described is also already stated within the user guide under the schedule command description as a warning, which should be sufficient as users would have read up on the command description beforehand and be aware of it. The meaning of each tag is actually also written in the developer guide, for developers who may not necessarily be familiar with their usage in the context of HR in order to understand what they mean, as shown below:

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: The users might not be able to view the Developer guide, but your developer can view the User guide. Hence, I strongly believe that providing this definition of the tags might be more beneficial in the user guide. I understand your point on "meaning of Offered and Rejected should be sufficiently self-explanatory for users" but I feel like it would be clear to state the constraints of these tags in the context of your app.

---