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.
The intention is to re-use the component from the check tool, so that we don't have multiple versions of the same thing floating around, and only have to maintain styles in one place.
However, we'll first need to break this out into a separate component.
Acceptance criteria:
The issues table in the check tool exists as a component in our library so that it can be used in multiple places and have consistent styling that only needs to be changed in one place.
Context:
Acceptance criteria:
Tasks: