Open Kappaccinoh opened 6 months ago
NotInScope - Great idea for future iterations but unsupported in the current version for now, users can edit the own professors' emails manually
Team chose [response.NotInScope
]
Reason for disagreement: I disagree with NotInScope and stand with low feature flaw.
The field that is concerned here is not just any random additional field, it is the field of an email, which happens to be a primary means of communication, and perhaps even arguably second to using a telephone number.
If Dook is meant to 'centralise faculty information in an innovative member' and to help 'manage their...contacts' (I have screenshotted your introduction of Dook from your UG), I would expect that the field of an email is of utmost importance (It doesnt seem very realistic or rather perhaps there has been a lack of consideration as a student using this application, that adding in their prof to the system doesnt give them their emails)
Furthermore, the main purpose of the add professor function in the first place (you went through all the trouble to make this feature and created a database of some form for 300+ professors), is for the purpose to have 'updated contact details at my fingertips', however the exclusion of the email fields in this feature is not mentioned in both the UG or the DG as to why (it could have been due to limitations in time or lower priority), but was not conveyed to the user.
Therefore, the lack of an email field is entirely within the scope of this feature, and should be explained properly as to why is was chosen to be excluded.
Adding in a professor's contact is a cool feature, however it is missing the email field which can be found on the NUS computing website
Following your UG, the purpose of the app is to keep in touch with people, both students and professors alike, I would imagine that having an email field is essential as contacting by phone number may be inappropriate or difficult if I want to send over files - searching for their contacts on the NUS computing website defeats the purpose of having a short cut.
I would argue that this is between a medium and low severity bug, however I will give the team the benefit of doubt.