Why do rating fields randomly show or hide themselves in "traditional" views?

Barry van Oudtshoorn
Contributor
June 21, 2023

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.pngScreenshot 2023-06-22 at 10.07.12 am.png

2 answers

1 vote
Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 23, 2023

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
Contributor
June 25, 2023

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
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 26, 2023

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 :) 

Like Steffen Opel _Utoolity_ likes this
Barry van Oudtshoorn
Contributor
June 26, 2023

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

Barry van Oudtshoorn
Contributor
August 6, 2023

Hi Atlassian team!

Can I check in on the status of this one? The support ticket I raised was closed because it was apparently just there to report the issue to engineering, rather than to get it resolved. (!?)

This remains a big impediment to my regular daily and weekly triage of items raised in JPD projects, as I have to keep jumping between my JQL-backed saved filter (which uses the "normal" JIRA issue view that exhibits this issue) and the JPD view (which can't do complex filters).

Is there a status update on this? An ETA on the fix? An explanation of what the fix will be? (Just getting the "normal" views back to kind-of-working, or going whole-hog with getting the "normal" view using the JPD issue renderer?)

Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 7, 2023

Hey Barry, 

We don't have an ETA for fixing it, because we are dependant on another team for this matter and also because we are focussing on Jira Product Discovery features. It is possible complex filtering in Jira Product Discovery is ready and released before this view gets fixed :/ 

0 votes
Omer Meshar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 22, 2023

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

Barry van Oudtshoorn
Contributor
June 22, 2023

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events