Open HemanshuGandhi opened 4 years ago
This bug was not related to the quality of documentation. Also, this bug was about an upcoming feature and not one that was already implemented.
Team chose [response.Rejected
]
Reason for disagreement: This bug is consistent with the definition of a feature flaw “Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less useful to the intended target user for normal usage. i.e., the feature is not ‘complete’. In other words, an acceptance testing bug that falls within the scope of v1.4 features. These issues are counted against the ‘depth and completeness’ of the feature.”
If the edit functionality (which is a basic part of CRUD operations ) is missing, then clearly this v1.4 deliverable cannot be deemed as being complete. I therefore argue that from a tester’s perspective, this fails acceptance testing.
The event management feature (under the scope of v1.4 features) will be incomplete if the user cannot even edit events (which is quite likely given typos, or that certain details of the event like description, place, or time will probably change).
Team chose [severity.Low
]
Originally [severity.High
]
Reason for disagreement: As explained in the reasons for disagreement, If the edit functionality (which is a basic part of CRUD operations ) is missing, then clearly this v1.4 deliverable cannot be deemed as being complete.
The event management feature (under the scope of v1.4 features) will be incomplete if the user cannot even edit events (which is quite likely given typos, or that certain details of the event like description, place, or time will probably change). From a user's perspective, given the nature of events, it is quite critical that a user be able to modify certain event details!
How useful is an event management feature if you cannot even manage the event by editing it?
although this is flagged as an upcoming feature in the UG, it is critical as part of the basic CRUD operations.