Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Using CSV issue importer with a field using the database-values-plugin

Is it possible to do a CSV import  to create issues when one of the fields is using the database-values-plugin to pull values from a remote system?   

When I attempt it using "Import Issues from CSV" under the Issues menu I get an error stating that the custom field value is null.

When I attempt it using "External System Import" under the admin menu I can import but the value shows up as Unknown id: [value imported].

I've checked the vendor documentation and did not find anything that helps.  Any tips or tricks would be greatly appreciated.

1 answer

I was able to track down the issue. The importer only allows the value of the remote database ID. Not the “name” column.
So when I attempt to upload using name value the cvs import fails. If I use the database ID from the remote DB table, the issue imports successfully. 

The format would be something like this:

Testing CSV upload,id:44b89e40-6232-11e5-8d1567890 {code}

Hi  @Sean Kennedy ,

I'm trying to update an existing ticket via CSV import and am having the same issue. I've used your suggestion above but still get an Unknown id: [value imported].

My query has 2 columns, 1) the internal id and 2) the name of the record returned.

The internal id field in the remote database is called "internalid". 

So I used the following on the CSV import:

  • Summary, Test
  • Customer, internalId:1779

Do you have any idea what the issue could be?

For reference, here is the file.

# The SQL Query that will be executed on the database
sql.query=SELECT internalid, entityId AS 'Customer' FROM [database]

# The column number (starting from 0) that contains the primary key of the returned data.

# The pattern that should be used to render the data in view mode. Use {column_number} as placeholders. You can use HTML, but make sure you close your tags properly!
# The pattern that should be used to render the data in edit mode. Use {column_number} as placeholders.
# The pattern that should be used to render the data in searcher. Use {column_number} as placeholders.
# This is used when sorting in the issue navigator. When not defined, the 'rendering.viewpattern' is used.
# Use 0 to have a combobox for editing, 1 to have AJAX-style input field, 2 for cascading select
# Use 0 to have a list for searching, 1 to have AJAX-style input field

jql.1.query=SELECT [internalId] FROM [database] WHEN entityId AS 'Customer' LIKE 'QUERY_VALUE%'

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Send an Email or Publish to Confluence - What should you do with your release notes?

Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...

125 views 1 2
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