Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

iqlFunction in Jira Insight not working for Customfield type "Insight Referenced Object"

Pontus Ridderström
Contributor
July 12, 2018

Hi

I am trying to utilize the iqlFunction("") in a JQL Query, when setting different SLAs as a specific attribute in a Insight Object Type defines what SLAs it is supposed to use.

I found the documentation how to utilize IQL in an JQL Query, with partial success. 
https://documentation.riada.se/display/ICV49/Insight+JQL+Functions

The problem that i have is that the Custom Field created utilizes the Custom field type "Insight Referenced Object (Single)" and i can not get the "iqlFunction("")" to work with that specific type. If i try with Another customfield with the type "Insight Object/s" i do get full functionality.

Is this a bug or am i missing something with utilizing the customfield type "Insight Referenced Object (Single)"? 

Will the function "iqlFunction" not be usable when developing an own customfield utilizing the Insight objects?

Best regards
Pontus 

1 answer

0 votes
Kirubel Tesfaye
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.
July 12, 2018

Hi @Pontus Ridderström,

Check this question which is similar to you in the link below.

https://community.atlassian.com/t5/Answers-Developer-Questions/Getting-complete-list-of-all-fields-using-JIRA-REST-Java-Client/qaq-p/509008

This will give you a list of "fields" from the JIRA Server which you can use.

Hope this helps!

Pontus Ridderström
Contributor
July 13, 2018

Thanks for your response @Kirubel Tesfaye
I am uncertain however how this actually answers my question. 

As i do not request to know the avaliable fields in the Jira Instance but rather want to know if the JQL function "iqlFunction("")" supports the Custom Field type ""Insight Referenced Object".

Best regards

Like # people like this
Antonina Khirnaya April 29, 2021

I also had this problem and eventually solved it.

Looks like the function doesn't work with translated fields as it searches somehow by translation (?).

As soon as I aligned the original field name with the current user language translation it worked.

Like Caigos Atlassian Admin likes this

Suggest an answer

Log in or Sign up to answer