Open Ongzl opened 2 years ago
We do admit that yes, it could be better if there are location or timing. However, we did not have time to implement this (we were short on manpower and this is legitimate).
Appreciate the tester's creativity to store the information in the event name. However retyping the entire event name to change the location/timing only causes minor inconveniences and happens rarely. The feature is meant to track attendance, there is no reason for the location/time to change once the event has started. The only reason for it to change is due to a typo which should not happen often at all. Even then, this is only a minor inconvenience.
Team chose [response.NotInScope
]
Reason for disagreement:
It seems to me that this event feature was added in at the last minute as lower priority features(chain commands and macros) were done first instead of a core feature (events), event table is not even mentioned in user stories , I do not believe this is NotInScope but instead poor planning at the initial stages and inability to rush for last minute addition/changes.
Team chose [severity.Low
]
Originally [severity.High
]
Reason for disagreement: [replace this with your explanation]
Only details shown are name of event and participants, this forces user to add in the details of the event into the event name which would make changing any details of the event very cumbersome as the user need to retype the entire event name to change the location/timing