You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the new graph, I am just confused about what the # column represents. Is it the number of absenses, the number of attendances or the number of the class session?
In the next sprint if you could clarify the way the table is labeled to make it obvious what data the table is displaying that would be great. Please let me know if you have any questions by leaving a message here!
The text was updated successfully, but these errors were encountered:
On Oct 12, 2015, at 11:08 AM, Steven Chambers [email protected] wrote:
Looking at the new graph, I am just confused about what the # column represents. Is it the number of absenses, the number of attendances or the number of the class session?
In the next sprint if you could clarify the way the table is labeled to make it obvious what data the table is displaying that would be great. Please let me know if you have any questions by leaving a message here!
—
Reply to this email directly or view it on GitHub.
I wonder if the class session number even needs to be there since there is also a date, its basically giving the same information in two ways, so its sort of redundant. I dont mind the info staying there, just change the label on the table so it would be more clear what that column means to an end-user
Yeah I can definitely understand where you're coming from there, even though this isn't my module. I will probably refrain from implementing a similar column in my version of it.
Looking at the new graph, I am just confused about what the # column represents. Is it the number of absenses, the number of attendances or the number of the class session?
In the next sprint if you could clarify the way the table is labeled to make it obvious what data the table is displaying that would be great. Please let me know if you have any questions by leaving a message here!
The text was updated successfully, but these errors were encountered: