Scheduled imports for Assets are here!
For a long time, customers told us: “Assets is the source of truth… as long as someone remembers to refresh it.” Now, that manual step is on its way out. We’ve started rolling this out to customers, so teams can finally rely on scheduled imports to keep Assets in sync.
With this release, you can automate recurring imports directly in your Assets object schemas, so your data stays fresh and trustworthy without the constant manual effort.
Why scheduled imports is such a big deal
Assets is at its best when it mirrors reality: who owns what, where it is, what it’s connected to, and what state it’s in. Meanwhile, the systems that “know” these things—device management, HRIS, cloud inventories, procurement, spreadsheets—are constantly changing.
Until now, keeping Assets up to date often meant one of these less-than-ideal patterns:
-
Admins running imports manually on a schedule (and inevitably missing a run here and there).
-
Teams building custom automation or API-based workarounds to trigger imports.
-
Data going stale—slowing down incident resolution, cluttering approvals, and skewing reports.
Scheduled imports addresses this head-on by turning import refresh into a reliable, repeatable background process—so Assets can stay trustworthy as your environment changes.
What’s included in the release
Once you’ve configured an import source for an Assets schema, you can now schedule it to run automatically at regular intervals.
Supported scheduling options
-
Frequency: once, daily, weekly, or monthly
-
Start date and time (selected in 30‑minute intervals)
-
Time zone: based on your Atlassian profile time zone
You can schedule common import types like CSV and JSON, plus other supported import types that appear in your schema imports list (including app-based imports where available in your environment).
How it works (and what to expect in the UI)
Scheduling is managed directly from the Imports page inside an Assets schema. After you save a schedule:
-
The import shows a Scheduled status lozenge in the imports list.
-
Hovering over the Scheduled lozenge shows the frequency and the next run time.
-
For one-off schedules (run once), the status returns to Enabled after the import completes.
Scheduled vs manual runs: designed to play nicely together
You can still run a scheduled import manually when you need to. Assets also helps prevent “double-runs” from colliding:
-
If you manually start an import less than 30 minutes before its next scheduled start time, Assets prompts you to continue or cancel.
-
If you continue, the manual import runs first and the scheduled run is queued to start after the manual run finishes.
-
While an import is running, the Imports page shows progress and disables the import button for that import until completion.
Operational visibility: history and troubleshooting
Scheduled imports use the same history and logging as manual imports. In Import history you can see:
-
When an import ran
-
Whether it was triggered manually or by a schedule
-
Whether it succeeded, failed, or completed with warnings
-
Who last updated the schedule (useful for auditing and ownership)
If a scheduled run fails, it’s recorded in the same place with error details—so teams can fix the source data or configuration and either rerun manually or wait for the next scheduled attempt.
Permissions and ownership: one important detail
Each scheduled import is associated with the user who created or last updated the schedule. If that user is removed from your organization—or loses the required permissions to manage imports for the schema—Assets disables the schedule.
Practical tip
For business‑critical schedules, ensure your scheduling owner is a stable role (for example, an Assets schema manager group member). If a schedule is disabled due to ownership changes, a schema manager or Assets app admin can restore it by opening the schedule details and saving again (which reassigns ownership to the saver).
Getting started (quick path)
-
Confirm you have permission to manage imports in the target schema (typically an Assets schema manager or Assets app admin).
-
Set up and test your import configuration manually at least once (or choose a run-once schedule first to validate it).
-
In your Assets schema, go to Schema settings, then select Imports.
-
Open More actions (•••) for the import, then select Create schedule.
-
Choose frequency and start time, then save.
Real-world example: keep endpoint data fresh without weekend work
An IT team maintains a central CSV export of laptops and monitors (asset tag, model, owner, location). They configure and test the import once, then schedule it weekly after the export job finishes. From that point forward, Assets updates automatically, the team can verify each run in import history, and service management workflows (like incident routing, approvals, and stock checks) rely on consistently current data.
Documentation:
-
https://support.atlassian.com/assets/docs/schedule-an-assets-import/
-
Forge Developer Doc https://developer.atlassian.com/platform/forge/queue-events-with-async-events-api-to-import-assets/#about-scheduled-imports
-
External Imports Developer Doc https://developer.atlassian.com/cloud/assets/imports-rest-api-guide/scheduled-imports/
-
Public roadmap item: https://www.atlassian.com/wac/roadmap/cloud/Scheduling-of-imports-for-JSM-Assets-schema-s?selectedProduct=jiraService&search=sche&p=72cebbc9-f6
-
Check out our other recent releases for Assets - Attribute Value Changed automation trigger and Unifying Assets across the Atlassian Platform
Was this helpful?
Thanks!
Karyn Findlay
9 comments