Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I'm curious if other qs devs have the same frustration or any work arounds for this.
I am referring to how QlikSense automatically hides axis labels, titles, legends etc.. based on some hidden predetermined breakpoints. See the screenshot below, and how the axis title is missing from the middle chart, and the axis labels are missing in the charts at the middle bottom and top right.
Example
Why the current functionality is frustrating:
And here is a random example I found from Tableau Public (https://public.tableau.com/app/profile/john.johansson/viz/HRAttritionDashboard_17728329067570/HRAttr...)
Look at the header with the tiny bar charts. As far as I am aware, out of the box Qliksense is incapable of rendering a bar chart that small. It will hide the axis way before it even gets close to that size.
4. Even if I manage to get the chart to fully render everything on MY monitor, if an end user has even a slightly different resolution or browser zoom it might still be hidden on THEIR screen. I then have to explain that this is just how QlikSense works and propose the following options:
QlikSense just seems very inflexible in regards to the types of layouts you can create unless you are ok with the charts having no Axis labels/titles or having very few charts. I wish there was a way to do some combination of the following:
So does anyone else have this same complaint/struggle?
There was an ideation request related to this back in 2020 that seemed to get traction at the time:
https://community.qlik.com/t5/Suggest-an-Idea/Allow-always-show-legend-and-X-Y-Labels/idi-p/1686483
Migrated Ideation link:
https://ideation.qlik.com/app/#/case/275038?cpid=bc5e21c7-f3a3-4242-a6bd-5046411c0ba3
I'm with you...
And this is despite this Ideation and extensions that allow you to shrink the chart size without loosing axis or/and label.
So I guess at the moment the alternative is to use 3 party objects I'm afraid.
A bar chart is usually the most commonly used chart in a dashboard. QlikSense is a data visualization tool and it's rough having to use a third party extension for such a fundamental chart because the native one has such a frustrating flaw.
Do you know if there's a better way to raise awareness for this issue?
Is there a minimum number of likes needed on the ideation page in order for Qlik to respond to/ consider the idea?
The lack of response/clarity is the other frustrating part. As I mentioned in my post its been in "on the roadmap status" since 2021 but I wonder if it's even accurate. It seems like when they migrated to that new ideation page many if not most of the ideas have been stuck in whatever status they were in at the time and haven't changed. For example many other ideas have been in "collecting feedback" status for 5 years too.
Hi everyone, thanks for the feedback!
Yes we are aware about this, and we are implementing settings to give the developers control on this matter.
For instance, the line chart and the scatter chart already have this:
Future updates to other charts will also add controls similar to this.
Hi Daniele,
I appreciate the response but I want to clarify just to make sure the problem is understood. We are talking about the Axis labels & Axis Title, not the Value labels.
This problem still exists even in the line chart.
I have recreated the image from my post with line charts instead of bars and as you can see
the axis labels and title are still being hidden just like they are with the bar charts. I'm using Qliksense November 2025. example line chart
Hello,
The post is about the axis label, not the value label.
Qlik should display moore information, the axis disappear ans if your laptop as a low definition, you can't display a lot of information in one page.
And the worst part is the gauge object, which requires an enormous size to display all the information.
Hi @devan9876
This is likely to be the most annoying thing about Qlik Sense.
The only alternative to prevent it from hiding (to some extend) on other definition screens is to set the sheet rendering to fixed custom resolution which in turn creates other issues.
Also - I voted and commented on the idea. Anyone else commenting on this post could do the same - vote and comment on idea to get more traction! @paulcalvet @robert_mika @Daniele_Purrone (i throw you under the bus here, Daniel 🙂 )
cheers
Here is another example to hopefully illustrate the point better. First image is powerbi, second one is Qliksese. Both same data and layout (6 equally sized vertical bar charts)
Powerbi has no problem fully displaying the bars, the axis labels, the axis title and the values. Qliksense is only capable of rendering the bars and the values. Whatever yall are using for the logic on whether there is enough space to render the axis is waaaay too agressive. For the record this is a problem in almost every chart, I just focus on bars because they are my most used chart.
Yes it is 100% the most annoying thing about QlikSense.
In pretty much every other aspect I prefer Sense over View & PBI but this one issue has been driving me insane for so long. I have similar complaints about the filterpane's behavior too but I'd settle for just getting it fixed on the charts 😞
Yeah, I agree fixed resolution has its own set of draw backs and doesn't fully prevent the chart from hiding stuff if you don't give it enough space. I'd like to keep the responsive grid mode, just without the charts auto hiding key components. It would be much better if they gave us more control over the breakpoints/padding.
And if I can really dream, imagine if instead of just pixels we could also specify the font sizes in terms of ViewPort (vh,vw) and/or Container (cqh,cqw) units so the font size of the labels could scale based on the size of the chart container or the entire viewport. That would be the best of both worlds between responsiveness and developer control imo.
anyways, thanks for tagging the others and encouraging them to vote!
Feel free to spread this post along to anyone else you know here who shares this frustration. I would love to see this finally resolved. I really do like QlikSense despite my negativity on this post I just feel strongly its visual restrictions especially in this area really hold it back.