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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Jira Insight Import file with a reference to another object

Hello everyone,

Im trying to run a CSV import where a particular import field needs to match an existing object type in Jira Insight.

For example, I am importing a list of custom hardware items that my organisation manages, where one of the fields is Hardware version. All existing Hardware versions are managed in another object type already imported into Insight.

In the new object attributes, I have defined the hardware version attribute as an object type and selected the correct object type.

When doing the import mapping (for the CSV import), it asks me to include an AQL reference. In this specific case, I have tried Label IN ${"BEE Version"} ( and some other variations) but I always get the following error:

Invalid placeholders in the AQL for attribute BEE Version. Placeholder BEE Version is not present as data locator

Anyone has an idea on how I can solve this?

Thanks so much in advance!

1 answer

1 accepted

0 votes
Answer accepted

Found out the issue. The data locator actually refers to the CSV column. So, it is about mentioning the CSV column on the AQL field and not the attribute of the object you are trying to match.

A bit confusing, but I got there in the end!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events