Schedule import of entra id assets data

[Nick Randazzo]

I am importing Asset data into Jira cloud from Microsoft Entra ID. The import works great now that it's all set up. Now I want to automate it so that it updates regularly without human intervention, but that doesn't seem possible with any built-in features that I can find. Automation Assets actions only include Create, Edit, or Lookup Objects. There is no option to schedule the import in the Assets schema for the Entra ID import. 

AI tools tell me I could create a Jira automation that calls an Azure Logic App and then triggers the import with a web call to Jira, but that seems so convoluted and I don't want to spend the time going through the effort only to find some roadblock with the approach.

Has anyone figured out a solid and relatively painless way to automate import from Entra ID into an Assets schema that is set up for an Entra ID import?

Thanks!

[Marc -Devoteam- · Accepted solution]

Hi @Nick Randazzo 

Welcome to the community.

The free provided option from Atlassian on the marketplace doesn't have tis function, the same applies if you want to use Assets Data Manager.

I did found this option, schedule-assets-import-using-automation 

You could try this out

You can get al the data, but not to import automatically ( not yet in Data Manager) or schedule the import.

If you want to accomplish this currently you would need to revert to paid marketplace apps.

[Nick Randazzo]

Thanks @Marc -Devoteam-

I will try the option you found. It looks straight-forward. I will post back here on how it works once I'm done. Many thanks for your help. 

[Nick Randazzo]

@Marc -Devoteam- this worked to trigger the import. However it appears to be "hanging". When I manually run the import from within the UI, it finishes in a little more than 1 minute.

With the automated trigger it ran for 17 minutes before I cancelled it. I'm trying again - let it run on schedule and it's ongoing for >13 minutes already. I can't see anything in the cancelled log. I'll let this run either until timeout or until I feel like it's just never going to finish. Any ideas about it in the meantime?

[Marc -Devoteam-]

Hi @Nick Randazzo 

Currently not.

Might be Atlassian Support can help out, as they can see the backend of your instance

[Nick Randazzo]

Understood. Thanks again for your help. Your solution did work trigger the import and it was super easy to set up.

[Lucrezia Mastrototaro]

Hello everyone, I am experiencing the same issue. The import freezes (sometimes for days) and remains in standby mode. I attempted to contact Atlassian, but they cannot access the logs as the app is in beta phase. Have you resolved this issue? If so, how? Any advice would be greatly appreciated at this time.

[Nick Randazzo]

I have not found a solution other than setting myself a calendar reminder to go click the button twice per day, which is sad. I played with some tools to do click macros to launch the page and perform the clicks for me but it was a waste of time and didn't work. It's a greatly useful tool and pulls the data neatly, but they have GOT to make it possible to automate it. 

[Wood_ Jeremy]

Hey @Nick Randazzo - Did you ever reach out to Atlassian support on this? If so, were they able to find any reasoning why it hangs on Fetching data? 

[Nick Randazzo]

I could swear I did and their reply was that it just wasn't supported because it's a free app, however I cannot find the documentation in my email. So maybe not. I'll give that a shot.

[Wood_ Jeremy]

I reached out this morning via Atlassian's automated system and got the below response. Sounds like we are stuck waiting for Atlassian to update this. ([JSDCLOUD-9920] Ability to schedule Assets Import ) 

---

 Thanks for sharing the details and the guide you followed. Based on the documentation and known limitations, here’s what’s happening and some next steps:

Key Points from Atlassian Documentation

• Manual vs. API Imports: When you trigger an Assets import manually in Jira Service Management Cloud, the process is handled directly by the UI and typically completes as expected. However, when using automation (via the REST API), the import process for certain types—specifically "Discovery" and "External" imports—relies on external software to initiate and process the import 1.
• Automation Limitation: The automation rule method described in the guide you linked is designed for JSON and CSV imports, where the file is already uploaded or accessible via a URL. It does not work for Discovery or External imports, which are initiated and processed outside of Jira by the Discovery tool or other external systems 1.
• Stuck on "Fetching Data": This is a known symptom when trying to automate Discovery imports via the API. The import gets stuck because Jira is waiting for the external system to push the data, which doesn’t happen with the automation rule alone 1.

What You Can Do

• Continue Manual Imports: For Discovery imports, continue to trigger them manually from the UI, as this is the supported method for now.
• Automation for JSON/CSV Only: If you need scheduled or automated imports, consider converting your data to JSON or CSV and use the automation rule for those formats.
• Monitor for Feature Updates: Atlassian is aware of this limitation, and you can watch for updates or feature requests related to automating Discovery imports.