Change Interviewer Status Command not working

[JukeBoxK]

The command for Change Interviewer Status is not working.

Steps taken:

1. clear the address book
2. add an interviewer with phone 81239123 add_interviewer n/Jane Doe p/81239123 e/janed@example.com
3. use the change interview status command interviewer_status 81239123 s/free

Expected:

Some message about interview status being changed

Actual: Error message about unknow command

[nus-se-script]

Team's Response

No details provided by team.

The 'Original' Bug

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

Bugs in UG

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

In the UG, (under features) theres no applicant_status and interviewer_status.

Since in the command summary there is applicant_status and interviewer_status, and they are also one of the main features, would be good to include them under features.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#5458] [original labels: severity.Low type.DocumentationBug]}

Their Response to the 'Original' Bug

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

The tester may have overlooked that there is indeed an applicant_status explained in the Features section of the UG titled "Adding a Status to an Applicant".

For the interviewer_status issue, we acknowledge this but argue that it is of VeryLow severity since we have a section for interviewer statuses in the UG titled "Viewing the Status of an Interviewer" that explicitly says there are no commands to set interviewer statuses manually as well as an explanation of how interviewer statuses work. The leftover interviewer_status in the command summary is thus a typo at best since we simply forgot to remove it. This may lead to a misunderstanding but would not necessarily lead to any harmful or incorrect behavior in the app.

Items for the Tester to Verify

:question: 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: [replace this with your explanation]

---

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---