It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

IQL Filtering for JIRA Service Desk Edited

Richard Winstock Dec 12, 2017

Hi

 

I have a multi-customer Service Desk Project, which uses Insight to provide various bits of information, all displayed via a set of cascading Insight Custom Fields.  I would like to be able to filter the customer fields using IQL.

 

I have a value against each Insight object called "Customer" which is equal to the value of Organization in JSD.  So my simplistic IQL would be

 

"Customer" = Organization

 

But this doesn't work - any ideas?

 

Regards

 

 

Richard

1 answer

0 votes
Alexander Sundström Dec 12, 2017

Hi Richard,

This is because there aren't any placeholders available in the IQL for the custom fields. According to your IQL, the Customer has to have the Label Organization, so it's not dynamically picking up the name for the Organization selected.


What can be done is to restrict a custom field to User Related Objects, it fetches on User type, Group type and Email default type attributes.

In that use case, you would have one field where you chose the organisation (Insight object, custom field), which you should be restricting to User Related Objects on the current user.

Then the other fields would be Insight reference fields, where you can select the objects references from the organisation selected in the first field mentioned.

Let me know what you think about the above approach.

You can read more about our custom fields at https://documentation.riada.se/insight/latest/insight-administrator-s-guide/insight-custom-fields where we have links to our different custom fields.

Best Regards
Alexander

Richard Winstock Dec 12, 2017

Hi - the "Oraganization" isn't a custom field really = it's a built-in JSD field.

 

The User Related objects is a potential option but as you've said would require the JSD Agent to select the Organization, and *then* select it again in an Insight field :-(

Alexander Sundström Dec 12, 2017 • edited

Yes, it's not an optimal solution, but the closest thing that can be done.

Just a thought, it should be possible using an post function to set the organisation field afterwards, and in that way only use the insight organisation field to restrict the other fields, and then when the issue is created, the "real" organisation field could be set by default to the same field as the Insight organisation.

Best Regards
Alexander

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted in Marketplace Apps & Integrations

Demo Den Ep. 4: Continuous Integration with CircleCI & Jira Software

Get ready! Demo Den Episode 4 is coming your way on Tuesday, May 28, 2018 with a Continuous Integration and Delivery special demo. CircleCI Director of Solutions Engineering, Eddie Webb will show us ...

626 views 0 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you