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?
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Hermance. I've raised this as JST-887940.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Barry van Oudtshoorn both snapshots are the same. Did you mean to attach a second different snapshot?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, they're definitely different from what I can see. :)
They do look very similar, but those pinned fields are different between the two of them. Both "Goal impact" and "Effort" are rating fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.