Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Insight - CSV Import, Filter data source by IQL using Wildcard/Like Edited


I am importing a CSV into Insight and I want to split the contents into different object types.

For instance (CSV example):

name, db_version

db1, postgres_11

db2, postgres_12

db3, MSSQL_2003

The object types in my schema, in this case, would be PostgreSQL and MSSQL.

On the data import, I want to put anything that starts with postgres into the PostgreSQL Object type. I.e. I would like to utilise a 'like' operator with wildcards. 

However, I have trawled the internet and simply cannot find an explanation as to how this is done. I have tried the below:

db_version like "postgres"

db_version like "postgres%"

db_version like "postgres*"

db_version like postgres

db_version like postgres%

db_version like 'postgres'

db_version like 'postgres%'

db_version like 'postgres'

(each of the above variations have also been tried with LIKE)

Please note - The fields are configured correctly and if I input a specific version into the Filter data source by IQL section, for instance:

db_version = postgres_12

The results are as expected and any entry with that version will indeed go into the intended Object Type. 

Any assistance you can provide here would be greatly appreciated! 


Dave W 






1 answer


I'm not 100% on that this solves the problem for you but I tested with this configuration and it seems to work fine. 

What is important to note is that the "Filter data source by IQL" is not run on the source columns but on Insight objects created during import. This means that you need to store the db_version into an attribute in the target object type - in my case I call it "DB version". 

In your case you may benefit to use inheritance to be sure your DB object types contain exactly the same attributes. 


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

850 views 30 33
Read article

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