Open TLChicken opened 2 years ago
This doesn't affect usage or reading and is perfectly comprehensible.
Team chose [response.Rejected
]
Reason for disagreement: Even though this possibly may not affect comprehension during reading, it is still a cosmetic flaw, and the reader will wonder why there is one extra header row with no content underneath. They may then question if the user guide has missing content since it contains a table with headers but no content rows. Hence this could affect reading.
Since this could potentially affect reading, the severity level could even be set as Low instead of Very Low, however I put it as Very Low instead as I also think that the chances of a reader getting confused is quite low.
Even if the chance of the reader getting confused from reading the table is low, a random extra header row is still a cosmetic problem regardless and thus is a bug.
At Page 19 and 20 there are 2 rows containing the same headers for the user stories table. There should only be one row.