-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tm_missing_data reporting issues #471
Comments
I agree. The card should have the dataset name since we're dealing with multiple dataset.
Good finding about reordering not being retain during the card addition. Since this is for missing data, I don't think the reorder matters as long as it shows the missing results. It would be great though if the card can also retain the reorder happened on-screen. I also think these issues should be in backlog. |
The first point is a one liner fix, the second point is probably because the table is a |
If the first point is a one liner fix, would be great to go ahead and address it in the UAT if feasible. I'm okay with putting the second into the backlog for next release if it's not that straightforward to fix. |
For the first issue, I'm fine with pushing the fix during UAT if the risk is minimal. Are we thinking about updating the card name and the content, or just the content? |
First issue is addressed here: #473 |
Moving second item to backlog |
Acceptance criteria: |
As discussed with @kumamiao, we don't need to have the report reflects the user-directed sorting. |
From #469
The report card doesn't actually say what dataset is being considered - maybe this extra line could be added inIs this what we want? Especially because when we reorder the table on-screen - it does not take the reorder into account when adding the tibble to the report card (should it?)
The text was updated successfully, but these errors were encountered: