Open ruiyangzh opened 12 months ago
We recognize this as a feature flaw; however we mark this bug as response.NotInScope
since we think that it's fine to delay the implementation of this to future iterations.
Moreover, in the UG we explicitly stated that this feature only support one schedule per person at a time:
As per requirement for response.NotInScope
:
Any further extension of this feature was, at the time, a relatively poor value proposition :
Tag
, as the UI space taken is much greater than Tag
(which is just one token!), in addition to further code changes to a newly-added feature.Note
(which, as you rightly pointed out, was flexible enough to partially supplant the need for this feature expansion!) was small that the team decided it was not a focus at the time.As such, we believe this qualifies as NotInScope
, given the trade-off in not pursuing feature extension.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Being only able to schedule one meeting is a relatively important feature flaw, since it is very much likely that meetings may be repeated or that the user may meet with the same contact multiple times. The user guide and developer guide do not provide justification, enhancements or workarounds to this feature flaw. This could be medium severity, but we choose low severity since you can work around this by using notes, even though this is not stated.