soc-pe-bot
commented
8 months ago Team's Response
I think the tester meant “this feature seems mostly there to correct any mistakes when starting a lesson by accident” instead of “setting a lesson”.
Going with this assumption, our team decided that limiting to “only 1 less than the number recorded” is good to have but was not what we planned. What we planned was simply allowing users to set number of lessons at on their own discretion, i.e. if they find other usages for setlesson, it can be beneficial for them. "Correction of accidentally start lesson" was just one of the many possible usages we suggested to them under the Tip box in
Another possible usage may be that a tutor realizes at the end of semester, a student only need to attend 8 out of 10 tutorials conducted for the full attendance marks. They can use setlesson to set all to 8 for easy overview of who attained 8/8 for the full attendance marks.
Ultimately, setlesson is a feature that we let users use at their own discretion. We decided it is not in scope because it may be a possible restriction of the command during future iterations.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
There is a fundamental feature flaw in set lesson. For example if a student has an attendance of 5/7 and we set lesson to 3, then the attendance goes down to 3/3. SInce this feature seems mostly there to correct any mistakes when setting a lesson by accident, there should be a limit of the number set being only 1 less than the number recorded. Eg we can only set 6 in this case.