Open germainelee02 opened 1 year ago
This issue is considered NotInScope, as this feature should not be prioritized over other features present in the current version. Additionally, there is no evidence in the assumption that forms the basis for this report ("In the real world, edit == EDIT").
Team chose [response.NotInScope
]
Reason for disagreement: If you want to use response.NotInScope
to reject this bug, you should at least show proof that you are planning to enhance this feature flaw. You did not write about command case sensitivity in your Planned Enhancements at all.
Additionally, there is no evidence in the assumption that forms the basis for this report ("In the real world, edit == EDIT").
When you say, "I want to edit this", it practically means the same thing as when you say "I want to EDIT this". You said there is no evidence in my assumption, but you also did not provide any rebuttal. If you can find a way of saying that 'edit' is VASTLY DIFFERENT from 'EDIT', then I will accept your response.
In the real world, edit == EDIT. hence the command word should not be case sensitive