Schedule an Assets import
Scheduled imports in Assets let you keep your asset data up to date automatically. After you configure an import source for an Assets schema, you can create a schedule so the import runs at regular intervals without manual action. Read more about how imports work and how to import objects into Assets .
You can schedule the following import types into an Assets schema:
CSV (Prepare your data for importing into Assets | Assets | Atlassian Support)
JSON (Import a JSON file into Assets | Assets | Atlassian Support)
Other supported types that appear in the schema imports list
You must have permission to manage imports in the target Assets schema. In most cases, you must be an Assets schema manager or Assets app admin.
Before you schedule an Assets import
次のことを行ってください。
Prepare your data for importing into Assets.
Set up and test an import configuration for your Assets schema. If you have not done this, read more about how to create an import structure, and how to prepare your data for importing.
Confirm that the source data is available and updated before each scheduled run (for example, the CSV or JSON file is in its source location).
Confirm the time zone set in your Atlassian profile; the schedule uses your Atlassian profile time zone.
If you don't have an existing import configuration that you’ve used before, create one and test running it manually at least once (or use the schedule frequency of ONCE) to make sure it works before you schedule it.
Create a schedule for an Assets import
You can create and manage import schedules on the Imports page in your Assets schema. There, you can choose the frequency of imports (once, daily, weekly or monthly), and specify a date and time to run an import.
Note that times are based on your Atlassian profile time zone, and that you can select times in 30-minute intervals after the current 30 minutes.
To create a schedule for an existing import:
In your Assets schema, go to Schema settings, then select Imports.
Find the import you want to schedule.
Select More actions (•••) for that import, then select Create schedule.
Complete the schedule details, then select Save.
After you save the 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 Scheduled lozenge changes back to Enabled after the import runs.
How scheduled and manual imports work together
You can still run a scheduled import manually when needed.
A manual run conflicts with an upcoming scheduled run:
If you manually start an import less than 30 minutes before its next scheduled start time, Assets will prompt you to continue or cancel the manual run.
If you continue, the manual import runs first. The scheduled run is queued and starts after the manual run finishes.
While an import is running:
A progress bar appears for users viewing the Imports page.
The Import data button for that import is disabled until the run finishes.
These rules apply to both manually triggered and scheduled runs of the same import configuration. To learn more about running imports manually, see Running an import in Assets | Assets | Atlassian Support.
Edit or delete a scheduled import
You can update or remove a scheduled import at any time.
To edit a schedule:
In your Assets schema, go to Schema settings, then select Imports.
Find the import with the Scheduled status lozenge.
Select More actions (•••), then select Edit schedule.
Change the frequency, date, or time, then select Save.
To delete a schedule:
In your Assets schema, go to Schema settings, then select Imports.
Find the import with the Scheduled status lozenge.
Select More actions •••, then select Delete schedule.
Confirm that you want to delete the schedule.
When you delete a schedule:
The import remains available and you can still run it manually or add a new schedule.
The Scheduled status lozenge is removed.
How failures and history are recorded for scheduled imports
Scheduled imports use the same history and logging as manual imports. These can be found in the Import history.
To see the Import history:
In your Assets schema, go to Schema settings, select Imports, then select Import history.
From Import history, you can see:
When an import ran (date and time).
Whether the run was triggered manually or by a schedule.
Whether the run succeeded, failed, or completed with warnings.
The name of the user who last updated the schedule.
If a scheduled import fails:
The run appears in the history with a failed status.
You can open the run details from the history to see error messages and troubleshoot the import configuration or source data.
After you fix the issue, you can either run the import manually or wait for the next scheduled run.
To understand structure-level differences between imports, such as changed or missing attributes, see View the structure status of an import in Assets | Assets | Atlassian Support.
How ownership and permissions affect scheduled imports
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 Assets permissions to manage imports for that schema, Assets disables the related schedule.
To restore a disabled schedule, an Assets schema manager or Assets app admin must:
Go to the import in Schema settings, then select Imports.
Open the schedule from More actions (•••).
Review and save the schedule details. Note, this will associate the schedule with the person that saved the schedule.
Keep your source data in sync for JSON and CSV imports
For JSON and CSV imports, scheduled runs always use the data that is available at the time the schedule triggers.
To avoid data drift and stale records:
Make sure your process to generate or update the JSON or CSV completes before each scheduled import.
Confirm that the file location or endpoint used in the import configuration remains the same. If you rename the file location or source file, update the import configuration before the next scheduled run.
Use the import history to confirm that scheduled runs complete as expected and that the data volume or object changes match your expectations. For an overview of all import types and flows, see What are imports? | Assets | Atlassian Support.
ユース ケースの例
An IT team maintains a central CSV file with all company laptops and monitors. They:
Configure a CSV import into an Assets schema to map fields like asset tag, model, owner, and location.
Test and run the import manually to confirm the mapping.
Set up a weekly schedule for the import to run every Monday at 1 a.m., after their internal system exports the latest CSV.
From that point:
Assets runs the import every week according to the schedule.
The import history records each scheduled run and who last updated the schedule.
The team only needs to maintain the CSV export process, rather than running imports manually.
この内容はお役に立ちましたか?