search

SampsonYe1999 / pe

0 stars 0 forks source link

`tag` field not recognized using the `copy` command #7

Open SampsonYe1999 opened 6 months ago

SampsonYe1999 commented 6 months ago

image.png

It is not specified in the UG that tag field is not recognized while using the copy command. It is useful to add in this functionality as well, since some users may want to know what tags are under the contact they want to copy.

nus-pe-bot commented 5 months ago

Team's Response

Same issue!

The 'Original' Bug

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

Copy command it UG does not specify that it does not work for tags.

Capture.PNG The UG does not specify that it does not work for tag, for example when I tried copy 7 tag, it tells me that the field is not recognised.

[original: nus-cs2103-AY2324S2/pe-interim#3164] [original labels: type.DocumentationBug severity.VeryLow]

Their Response to the 'Original' Bug

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

As per the UG, in the first sentence of the screenshot above, it is mentioned that copy only works for fields such as name, phone number, address and email. Other fields (be it tag or other words) that are input into the command should hence be believed to be invalid fields.

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)

Reason for disagreement: [replace this with your explanation]

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** The phrase `such as` is used for example listing, it does not mean that whatever things listed after are completely comprehensive. You should use the word `only` in your UG if that's what you intended. In that case, I do agree this is a documentation bug which your team should not reject.
## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FeatureFlaw`] - [ ] 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]