MoM of Feedback Portal - Githubissues

Attendees : vlead staff Date: 16/09/2016

Response is not a good word need to have a better word may be qa_pair
User credentials need to be captured. eg: user_id
Requirements need to be sited to meeting minutes. eg: issues 1014, item 10.
how many labs does not have feedback. ( this number need to be captured)
how many labs have feedback. (out of 114)
radio buttons should be displayed down (take care in mobile version)
In feedback form, rating descriptors need to be displayed.
=lab_id= also need to be captured and displayed on the form.
Requirement satisfied links need
user city and town need to be added in user registration so that it can be used in feedback. (used for analytics)
scenarios need to be defined along with requirements or use cases need to be defined)
edge cases and corner cases need to be taken care
=feedback_usage_by_workshop= need to be changed to feedback_usage.
=workshop_set= need to be removed. name something else. usage by ip and date
Assumptions section need to captured in the model.
=date= need to be captured from the machine itself. (take from the server).
total number of test cases need to be defined.
Systems team will give api by EOD.
no need of re-direction because vlabs can also use this feedback form.
form need to have version number displayed
old feedback data need to be migrated or not

vlead / feedback-portal