nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why does a search for JQL perfectly confuse users?

Anselmo

The best Google hit I found for "JQL" was this blog post: Search JIRA like a boss with JQL

But following the highly recommended favorite link there, is completely misleading (not my sense of humor).

In all of the split spaces (what the heck...) I don't have a good hit with the term "JQL" anymore, besides the fact, that the titles of those three new clouds don't tell me at all, what to expect there. "Core" is bullshit and depends highly on the target group which claims for itself what's core from its very specific perspective.

For me as a stupid user it is essential not to make choices first, if I want to learn something new. I request to be guided adequately! But this went totally wrong and I'm really pissed.

Accepted answers

Inactive Stephen

Hi @Anselmo

What is it you're trying to learn?

There are still plenty of guides and details on JQL in the Knowledge Base - for example, the third result on Google for me was this page, with details on both Server and Cloud for JQL.

If you're looking for something specific - happy to try and direct you to the right place or offer advice on how to resolve

Ste

All comments

Inactive Stephen

Hi @Anselmo

What is it you're trying to learn?

There are still plenty of guides and details on JQL in the Knowledge Base - for example, the third result on Google for me was this page, with details on both Server and Cloud for JQL.

If you're looking for something specific - happy to try and direct you to the right place or offer advice on how to resolve

Ste

Anselmo

Thanks for that hint. I'm so tired of trial and error I have to do all along, because folks don't move their shit out of my way. It couldn't even look worse in my cellar.

Creating content quickly is nice. But all created content should have a kind of auto delete date if it wasn't taken care of for two years. For this a valid machine readable statement would be necessary whether something was found useful or not. A timer could show, how much "fuel" a page still has. If nobody is willing to refill, it should definitely die and leave space for better content. Virtual fuel is for free.

In times of accelerated change we need to get used to not being able to keep content, just because parts of it may still be valuable. Content has to be reinvented permanently somehow anyway. And if you water and fertilize your beloved plant, it will not die. It's just the fire and forget documents, which will not serve anybody positively all too soon.

So the difference between a living documentation and a dead one is attention which is invested on it regularly. But I cannot accept, that my attention is stressed exorbitantly by ever growing and more and more irritating content.

Tom Lister_fo1j4e

I regularly share this article with our users and they find it useful

This vid is a tad more digestable

https://www.youtube.com/watch?v=_z9uzmLSlP8

Anselmo

Yes, you are right, Tom. This is much easier to grasp.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-core

jql