The current implementation of the dataset issues page is that we're playing issues back to users on a per-entity / per-record basis, meaning that users have to click through each entity/record to view the details of the issue.
This isn't a great user experience when the user is faced with a high volume of issues.
A better experience would be to display this data back to them in an aggregated format, in a table.
Context:
Acceptance criteria:
Tasks:
Designs:
@alextea to add