Open rertyy opened 5 months ago
Thank you for the feedback! Can we clarify what you mean when you refer to 'bugs', because our error message was not liable to change in v1.4.
Team chose [response.IssueUnclear
]
Reason for disagreement: To screenshot my initial message:
The first few lines mentioned that the command should have been accepted, but it is not. And that is the bug.
The below information not relevant to the bug itself, but regarding your stance on v1.4 allowed changes. Regardless, whether or not you were allowed to change it in v1.4, it is still a bug, and I see no reason why "not liable to change in v1.4" is any reason to be not consider it a bug.
In v1.4, you are allowed to change error messages if they are wrong. Source: #659
I admit I made an error in my initial issue. I meant to say that you put it under "Known Issues" in UG, but it should be in "Planned Enhancements" in DG (see here) but the bug I reported still stands.
To reproduce: e.g.
edit 2 -n DBS -p 91234567999001 -t /aa/aa
Error message shown when it should be accepted
Criteria for rejecting bug: You put it under future enhancements
I put it as low because you mentioned it in your UG, and this is a bug that you could have fixed in v1.4