-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
EUI <> AnalystXP Priorities #182611
Comments
Pinging @elastic/eui-team (EUI) |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
Hi @ninoslavmiskovic and @teresaalvarezsoler, @timductive has put a list of issues together that he would like EUI to help with as part of our current prios for Discover and Dashboard. @JasonStoltz has assessed these from an EUI perspective with regards to effort / value, but it would be really helpful to combine that with your input with regard to how useful they are for your team's current and future efforts. Would you be able to evaluate these issues and add a comment below with each issue listed with a Must have , Nice to have and Don't need... and simple explanation if needed. We (Jason / EUI) will then take this input and work out which issues to focus on. Thanks, and let me know if you have any questions. |
From my perspective the data table /datagrid enhancement are important since we are making changes as part of the "One Discover" initiative and could be very handy to get fixed. |
Hey team. I'm piecing together a recap here from various conversations I've had with folks. This is simply my current thinking, and nothing here is definite. I'm posting this in advance of when we meet next week to help organize ahead of time. High priorities Medium / unclear priority Low priority / won't fix FWIW:
[EuiDataGrid] Allow sticky columns #2839 |
One more bug-related issue to add to the discussion if we have time: |
@timductive I added #7828 to the high priority list. Thanks for adding that issue. I also updated my comment with all of the notes from our meeting if you'd like to review them. |
looks good, thanks @JasonStoltz |
Adding a new one, which is important for our Contextual Logs Presentation : elastic/eui#7835, added it to the list |
@JasonStoltz This is high priority also as part of One Discover initiative. Could you please take a look and estimate the effort. Thanks |
@ninoslavmiskovic I'll review this one with @kertal, I'm not sure I understand the ask. |
[Update] By Jason S. to reflect correct priority.
The following tasks are important to solve between EUI and Kibana.
High priorities
Effort: Large
This seems like really bad UX and should be something we fix ASAP. Our plan is to fix this by implementing
Effort: Large
Partially completed.
Auto Fit
behavior whenCell row height
-Custom
is selected eui#7835verticalBoxes
icon button eui#7660x
clear button eui#7289Medium priorities
Effort: Large
Keyboard only usage is important to users, so this should be a priority.
Low priority
onFullScreenChange
callback eui#7604Effort: Medium
This appears to be tech debt, as there is already a work-around in place. However, Tim asked to put this at the top of our tech debt queue, which the EUI team will do.
Effort: Medium
It appears that something custom is being used, and we'll consider it for EUI in the future if it performs well in production.
Effort: Extra Large
We're not sure at this point if it's technically possible or not, our underlying library, react-window, explicitly does not support this. Tim and Nino advised that if this is a very large effort, it's OK to deprioritize for now.
Effort: Large
Core issue is the use of nested popovers, which shouldn't be used. Solvable via redesigning the dropdown. Discussed with Tim and Nino - Michael M. to help redesign and it will go back to Tim's team to work. Low priority for now.
Effort: Medium
Low value / questionable value.
Effort: Small
This seems very minor and @teresaalvarezsoler mentioned that she's not sure it's affecting dashboards/lens/discover UI. It's also been a known issue for over 3 years now.
Effort: Large
Large effort/low value -- per @teresaalvarezsoler "I think this is a nice-to-have, unless this is a super quick fix, we can cancel it."
The text was updated successfully, but these errors were encountered: