-
Notifications
You must be signed in to change notification settings - Fork 21
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
Include Data Souce type in drop-down list #372
Comments
Let's also open this issue upstream since I know @arikfr talked about improving this there. That way it'll get more attention. |
@fbertsch Do you mean on the data source dropdown on the create new queries page or somewhere else? |
@alison985 in the dropdown list, where users select the data source, is where it would be most useful. |
@alison985 I would hold off on this for the moment though, we're working on a strategy for making data sources more obvious. |
@alison985 Please let me know in case you want to work on this as collaborating with the upstream Redash team on this big feature is a requirement to move forward. In recent months we've coordinated more with them and have had preliminary discussions about how this could look like, and want to stop adding on top of our fork to prevent further technical debt. Of course @fbertsch's input as a Redash user is welcome to clarify use cases and work out the feature set. |
@fbertsch I'm wondering if you know where this stands right now? We've been doing some user research for Redash and unclear/undocumented data sources is a big concern that frequently comes up. |
@emtwo some of this already happened, e.g. sorting the list and renaming some of them to something more obvious. We had some additional work around: descriptions, owners, etc. but I'm not sure what came of that. @robotblake had taken ownership of that, IIRC |
This enhancement would make it a bit clearer when looking through the data sources; have e.g. the icon and name for each data source type available on the right side of the drop-down list.
The text was updated successfully, but these errors were encountered: