You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I created an Insight custom field called 'System' that should display and select objects with object type 'System' (a custom schema and object type).
When I enter just this (no order by clause) it works fine:
But when I add the 'order by' clause (I tried multiple attributes), the drop down does not return anything ('no options avalable' and a popup screen on the botrom right informs me it didn't fetch results'
The same IQL query runs fine when I use it as a filter in the Insight screen itself. So the syntax is correct. It's just that adding the 'order by' clause is causing it to fail in the custom field?
Any ideas if this is a bug or am I doing something wrong?
Thanks for your reply @David Sumlin
For another field, I do need the Issue IQL to filter on field values in the issue, but for now I'm just trying to make the ORDER BY work.
I tried the following combinations and all have the same result (no options in the dropdown and a popup screen says 'didn't fetch results'):
attempt 1 (from my original post):
Do you have an example where the ORDER BY works?
@Pieter Wouter Hartog , is it possible that the label identifier/tag is on a different attribute than the Name attribute? I'm assuming you're displaying the objects in the custom field using the label attribute.
Normally, I put my ORDER BY clause in my Filter Scope (IQL) and it works as expected. (e.g. objectType = "Domain" AND Status = Active ORDER BY label)
@David Sumlin Thanks for your example.
You are also working with JSM Cloud?
The exact same thing doesn't work for me; as soon as I add the ORDER BY clause in any of the two fields, the IQL stops returning anything.
I will log a ticket with Atlassian to see what's going on.