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 do rating fields randomly show or hide themselves in "traditional" views?

Barry van Oudtshoorn_srd8ie

When viewing discovery tickets in the "traditional" view -- for example, as a result of a JQL query to more effectively triage and review new items -- rating fields (such as "effort" or "goal impact") seem to be visible for only about 20% of tickets, and I can't find any rhyme or reason to it.

Here's an example of a JQL query I ran this morning -- and you'll see that for one ticket, the "Goal impact" is visible, whereas for the next one in the list, it's not! 🤷 Is this a bug, or is there some deeper design at work that I just don't understand?

Screenshot 2023-06-22 at 10.07.06 am.png

Accepted answers

All comments

Omer Meshar_0f60qw

@Barry van Oudtshoorn both snapshots are the same. Did you mean to attach a second different snapshot?

Barry van Oudtshoorn_srd8ie

Hmm, they're definitely different from what I can see.

The first has AX-148 selected, and the pinned fields show "Goal", "Goal Impact", and "Effort"
The second has AX-147 selected, and the pinned fields show "Goal", "Region", and "Class"

They do look very similar, but those pinned fields are different between the two of them. Both "Goal impact" and "Effort" are rating fields.

Hermance NDounga

Hey Barry,

Thank you for reporting this issue. Since I noticed you are in the new issue search experience, I went and tried myself and I have the same issue, not only with rating fields actually, and not following any specific pattern.
The only workaround I could find was to go back to the "old" experience (it depends on your site and permissions but you might be able to disable it using the three dots in the top right corner of the screen).

I'm raising this behavior to the right team internally, but if you could open a support ticket at support.atlassian.com/contact it would highly help us investigate the causes of the error.

Thanks for your feedback

Hermance

Barry van Oudtshoorn_srd8ie

Thanks Hermance! Unfortunately I can't raise this with support as we haven't yet completed moving to the paid version of JPD. Once we get that done, I'll check back in and see if it'd still be useful to raise it as a bug that way.

Hermance NDounga

In this specific circumstance, while the bug is on Jira Product Discovery fields, it happens in the Jira Software interface (and we haven't tried, but it might happen for other Jira products. Your support ticket will be accepted, especially since we need to investigate this issue

Barry van Oudtshoorn_srd8ie

Thanks Hermance. I've raised this as JST-887940.

Welcome!

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