Open PokezardVGC opened 1 year ago
Thanks for bringing this up! However, after thinking this through, our response is that, in the context of the find
command, as all the searches are based on what is displayed in the respective cards (i.e. in this case, each issue
card in the issue list that shows the details of the issue). here, we may note that completed
and incomplete
are shown as the status of each issue and therefore, for the sake of both consistency as well as ease of user reference (where he may want to look at the issue card to see the fields he wants to search by), we have to retain the design decision of having s/incomplete
and s/completed
.
Moreover, in terms of general language use, completed
might be more intuitive for an issue already finished (as it is in the past tense) and incomplete
better captures the state of the issue (currently not done - present tense). Furthermore, the correct label should be FeatureFlaw
instead of FunctionalityBug
as this issue (bug report) deals with a design decision. issue -f s/completed
and issue -f s/incomplete
work as has been mentioned in the UG and therefore this is not a FunctionalityBug
.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
Team chose [type.FeatureFlaw
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your explanation]
A little inconvient to differenciate between "completed" and "incomplete" since need remind to put past tense for completed