User Details
- User Since
- Apr 14 2012, 12:13 AM (657 w, 12 h)
- Availability
- Available
Nov 7 2018
@epriestley we are using the "menu item" solution that you described above, and the primary remaining pain point is that when you click on a link, the menu highlights "workboard", which confuses some users, because they expect the link (i.e. the menu item they just clicked on) to be highlighted.
Dec 17 2015
Dec 11 2015
Feb 19 2015
@epriestley and @chad - wanted to follow up and hear your thoughts on this if you've had a chance to review
Feb 9 2015
Happy to provide some background. This is for tracking the per-component breakdown of tasks for MemSQL's database engine. We'd be happy to jump on skype/hangouts/webex/whatever and let you poke around our setup if you'd like.
We're also pretty happy with the current behavior when the page is too small - the tabs just neatly display over two rows instead of one. It enables jumping to a specific tab very quickly in the interface.
Can you suggest an alternative for producing this kind of report? In our case, each tab corresponds to a component in the engine, and it would be valuable to visualize the total task count per component in dashboard.
For context, this is for organizing tasks at MemSQL for the database engine. We use projects to track releases and want to use a dashboard to build an overview of how each component of the engine is doing. One of the views is a query over all failed tasks, split up by engine component. I built a visualization in dashboard for this today, and we ended up with 12 components (1 tab per component). It looks/works quite well with 12 tabs.