nus-se-script
commented
1 week ago Team's Response
Thanks for the feedback! While we do agree that the current UI may not be the most optimal in tracking attendance turnout patterns visually, we disagree with its lack of ability to track how active a member is over time. The given session dates most definitely give concrete data for tracking when a member is present for a session or not.
It was also mentioned that it was "almost impossible to track attendance turnout" too. However, a simple use of the attendance command allows the user to view a list of all members and their attendance status for that day's CCA session. Additionally, it was mentioned under our planned enhancements that we're looking to implement a future feature to view the attendance of all members by date (and not just the current day).
As such, we deem your feedback as NotInScope, as while it may be better to make the attendance dates visually more optimal for tracking attendance patterns, it appears to be more of suggestion. It was also addressed as feature coming up in future versions!
Nevertheless, thank you for the feedback!
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: I understand your future plans to allow viewing the attendance on any specific date, instead of today's date. However I believe that viewing attendance data in aggregate (e.g across a month / semester) is a very basic feature of attendance trackers, and should have been implemented from the start, not left as a future enhancement. More specifically, CCA leaders should easily be able to see how many trainings / CCA sessions were missed in the past month / past semester to determine if a member is putting enough effort into the CCA and fulfilling attendance quotas. However, the way the attendance system is displayed now, without special UI features indicating CCA sessions that have been missed and with all sessions displayed as date chips, makes it unreasonably taxing for CCA leaders to find out that info, especially across a whole semester.
Imagine you are a CCA leader of a sports CCA training 3-4 times a week (as most sports CCAs in NUS do). You are trying to see which members attended less than 70% of CCA sessions across the previous semester so that you can reach out and encourage them to come for more trainings. One semester = approximately 10 weeks of trainings = 30 - 40 trainings and 70% of that is 21 - 28 trainings. With the current date chips attendance UI, the CCA leader is going to have to count all date chips of each member within the range of the semester and make sure that the member attended at least 21 trainings This is unreasonably time consuming for a task that people would expect should be easily done with an attendance tracker (finding out how many trainings a person was present / absent for within a time range).
Because of how time consuming it is to perform the basic attendance operation illustrated above (finding out how many trainings a person was present / absent for within a time range), for a rather common type of CCA (sports CCAs / CCAs having sessions 3 or more times a week), I think the attendance UI is not fulfilling its intended function of tracking attendance of members sufficiently, so it should not be a "response.NotInScope".
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** This issue would inconvenience a rather large group of CCAs which are quite commonly found (CCAs with sessions 3-4 times a week, e.g most sports CCAs), so it would cause occasional inconvenience, instead of rare inconvenience. Hence I feel it should be a "severity.Medium" instead of a "severity.Low"
One of the main functions for this app is to mark attendance of members for attendance tracking. However the view panel displays the sessions attended by the target person in individual chips. This makes it very hard, almost impossible to track attendance turnout or how active a member is in the CCA over a period of a few months or more, which is one of the primary functions of attendance tracking in the first place.