Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,773
Community Members
 
Community Events
176
Community Groups

Insight custom field does not support order by?

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:

  • Filter Scope (IQL): objectType="System" 
  • Filter Issue Scope (IQL): objectType="System" 

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'

  • Filter Scope (IQL): objectType="System" ORDER BY Name ASC
  • Filter Issue Scope (IQL): objectType="System"  ORDER BY Name ASC

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?

 

2 answers

1 accepted

0 votes
Answer accepted

I contacted support and they confirmed there is a known bug in Jira Cloud for this: https://jira.atlassian.com/browse/JSDCLOUD-9885

Please vote for this bug when you experience this issue as well.

Unless you're going to filter your values in the custom field based on values from the issue, you don't need the Filter Issue Scope (IQL).

After that, you should be able to add the ORDER BY clause to the Filter Scope (IQL).

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

  • Filter Scope (IQL): objectType="System" ORDER BY Name ASC
  • Filter Issue Scope (IQL): objectType="System"  ORDER BY Name ASC

attempt 2:

  • Filter Scope (IQL): objectType="System" ORDER BY Name ASC
  • Filter Issue Scope (IQL): none

attempt 3:

  • Filter Scope (IQL): objectType="System" 
  • Filter Issue Scope (IQL): ORDER BY Name ASC

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.

Ahh, I'm on Server/DC, so maybe it's different there.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events