Katie Hindson

ya, I'm not too sure about the best UX for this. Here are a couple more options in my mind: 1. We keep the `created-by-lightdash` tag, then just explain in...

Closing this as not planned - it's written up in the docs on how to do this. We can always reopen if another user runs into this issue!

ah yes, symmetric aggregates: Looker's secret sauce. We have an open issue for dealing with symmetric aggregates here: https://github.com/lightdash/lightdash/issues/961 Defining the join relationships will definitely help with this too! (if...

Hey @olly-writes-code . I'm not sure that defining the joins alone will solve your problem here? I think actually what you're interested in is this issue: #961 To be clear,...

👋 Hey Mincho Thanks for opening this issue. When you say `custom dimensions` - do you mean the custom dimensions that you create from within the explore view? ([like this](https://docs.lightdash.com/references/custom-fields#custom-dimensions))...

Just adding another bit to your comment here from Slack, John! If you then omit the title and choose any header smaller than H4 at the single row option then...

>Hi Katie, right so this existing issue is similar to what we are requesting, but our user is actually looking to not having to navigate into an additional pop-up modal,...

oooh interesting - I've never seen `grouping sets` before 👀 Let me just triple-check I understand what you're saying here... If I had `unique users`, for example, then the total...

Another user requested this! They want it on a per-project level because they share projects with partners they work with to keep the data separated between partners. SO it wouldn't...

@Ovilia I'm confused - how is this not a bug? It feels like bars aren't **_meant_** to overlap axes, or even appear _**fully outside**_ of an axis, like this: ...