Skip to content
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

Analyses Sections Redesign #19

Closed
jstiehl opened this issue Aug 29, 2017 · 1 comment
Closed

Analyses Sections Redesign #19

jstiehl opened this issue Aug 29, 2017 · 1 comment
Assignees

Comments

@jstiehl
Copy link
Contributor

jstiehl commented Aug 29, 2017

Currently the analyses sections in the dashboards are just list of analyses that link to the dataset that the analyses were run again. The dataset can be filtered by app and app version and sorted by date. See below.
image

There is probably a better way to display this data. Perhaps by grouping the analyses by dataset? Filtering by user who ran the analyses (for Public Dashboard)? Other ideas?

The expected outcome of this issue is to provide preliminary recommendations for UI updates that might improve the user experience with the Analyses sections of the application.

@chrisgorgo
Copy link
Contributor

I am pretty happy with how this view looks like right now. The one addition I would think of is color coding status.

I see three use cases:

  1. User wants to see their most recent jobs (to check their status) - current default view serves this issue well.
  2. User wants to see all jobs run for a given dataset - this is relatively easy by going to the dataset page, one improvement I would suggest is to flatten the hierarchy of folded boxes so getting to results would require fewer clicks.
  3. User wants to see all public jobs of a particular app - this is possible with filtering of the public dashboard, but in the future I see this being also a part of dedicated "app library" section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants