Forums

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

Insight IQL - Objects based on user and object location

Deleted user August 7, 2019

Hi there,

I think I don't totally get the whole IQL stuff. Among others I have the following object types: user, printer, location

- The user objects have an attribute with a reference to the corresponding Jira User ("JIRA-SOFTWARE-USERS") and one the refers to a location object

- The printers objects have, among others, an attribute that refers to a location object


Now I want, that when a user, e.g. sitting in Berlin, creates an issue, he can only choose the printers, that are installed in Berlin.

So my custom field has a filter scope objectType = printer but how might the filter issue scope look like?

Thanks in advance!

1 answer

0 votes
Nader Nassif
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.
August 14, 2019

Hi Christian,

I would recommend that you invest some time to learn IQL. It's really easy and unlocks the full power of Insight ;) 

You can watch this video to get a glimpse on how to use IQL  

The use case described is incomplete in my opinion. The reason is because, though have a location attribute on the user and the printer object but when according to you when a user creates an issue they do not choose their location. Insight does not include a function to auto detect the IP and determine the location of a user. They should choose their location from another field.

Let's say you have customfield_XXXXX with location and customfield_YYYYY with the printer. For the first one you will set the objectType = Location and choose the location from it. The second field will have objectType = Printer and you can use this IQL in that case : 

object HAVING outR(Label = ${Location}) . This will allow the user to only pick the printer with the location added as an attribute.

In that sense, the location attribute on the user object will not be used.

Cheers!

Nader

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events