New feature: Import and refresh Insight data from a URL

[#1]

Hello Community!

We’re excited to announce the launch of a new feature that allows Insight admins who import CSV or JSON files to pull their data directly from a URL, instead of manually creating and uploading files. Once linked, data can be refreshed with the click of a button, without the need to set up a new import.

For detailed information and step by step instructions on how to set up an import from a URL, please refer to our documentation on Atlassian Support.

To find out more about imports for Insight in general, refer to this article.

PLEASE NOTE:

As a first iteration of this feature we only support public and secure web addresses (https). We are looking to expand this functionality further in the future by adding authentication.

In the meantime, exposure of URLs can be restricting by granting access to the 'Atlassian domains' only as outlined here, and in more granular shape here.

[Kalin U]

Hi. Excited to try this out. I have a couple of questions:

1. Will the import duplicate objects if the CVS file contains previously imported data? In our case, we are interested in importing users.
2. Do you have any suggestions as to how this CSV/JSON import from a URL can be scheduled? I understand that this works manually, with the touch of a single button, but it still requires a person to do it :)

Regards!

[Dirk Ronsmans]

@Dorothea Linneweber ,

Excellent first step! I think the showstopper might be that it has to be a public (unauthenticated) url for now. Maybe a next iteration could be something with a OAuth2 authorization or token of some kind?

Looking forward to both iterations of this feature (we like to use Sharepoint to host the import files or putting them on OneDrive with a share link?  so using a O365 token or something would be great!), scheduling of course..  and future import sources ( *cough* Azure AD and on premise SQL ;-) *cough*) but liking the progress being made!

[Cristian Iorio]

This is great, the feature has been long-awaited !

[Gary Blower (Clearvision)]

The recent API changes mean you can also trigger the import on a schedule using Automation.

You'll need to create a scheduled automation and the Web Request action.

Steps

1. You need to encode your credentials "<EMAIL>:<API_TOKEN>" with base64. You can make this through any online tool like Base64 encode.
2. You'll need the Workspace ID and Configuration ID from Insight.
3. The Configuration ID can be found on the Import Configuration Details (schema > config > import > import history > details).
4. The Workspace id can be found using this URL 
   https:// <JSM Premium Site Name> .atlassian.net/rest/servicedeskapi/insight/workspace
5. Finally you can create the Automation WebRequest action using a POST on /import/start:

• Web request URL: https://api.atlassian.com/jsm/insight/workspace/<workspace id>/v1/import/start/<configuration id>
• Authorization: Basic <encoded creds>
• Content-Type: application/json
• Accept: application/json

 

[Dan C]

Assuming this is cloud only?

It'd be really helpful if all Atlassian posts could clearly state if something is data center, cloud, or both

[Kalin U]

@Dan C , the article has been tagged cloud.

[Dorothea Linneweber]

@Kalin U to answer your questions further above:

1. Duplication of data
   • Data won't be duplicated as long as the identifier remains the same. It will be overwritten with any changed information.
2. Scheduling of URL import using automation
   • As @Gary Blower (Clearvision) mentioned, there is a way to do this using Automation.
   • We do however want to call out that this solution has the api token stored in an automation rule which is not encrypted, only a plain text which is a security vulnerability. Depending on your use case this may not be too much of a concern but please be aware.
   • We are absolutely aiming to make scheduling available for imports moving forward, but are still working through some dependencies before we can commit to a timeline. Please bear with us.

@Dirk Ronsmans absolutely hear your concern around the risk of a public URL. As mentioned, adding authentication will be our next iteration on this feature, although we can't commit to an ETA just yet. In the meantime, exposure of URLs can be limited by restricting access to allow only the 'Atlassian domains' as outlined here, and in more granular shape here.