| Table of Contents | ||
|---|---|---|
|
| Info |
|---|
The Scheduler Cloud with version 3.6.0 introduces possibility to import SI. In the documentation the process and all its features will be explained. |
Exporting SIs
Let’s start with option already available in the past which is Export to CSV. While having SIs, above SI table there’s a button allowing you to export current SIs and their subtasks to .csv file.
...
Exported .csv can be viewed and edited for example in Notepad++ or Excel through Data → Get Data → From File → From Text/CSV for easier to read view.
...
Exported SIs can be now imported through option Import from CSV located above SI table.
...
By clicking import button a small window pops up that allows to choose which .csv file to import.
...
| Info |
|---|
You can view timezone of imported SI be clicking 3 dots on the right and click Edit triggers.   |
SI Import and duplicates
When importing a lot of SIs may happen that some of the names may reoccur. During import when list of SIs is read from the file Name conflict warning will appear. You can change the name of SI by clicking on it and typing a new one, skip duplicated SIs or override them.
...
Duplicates - Override duplicated
...
Here we choose Override duplicated. By click this option duplicated SI will be marked with a warning mark.
...
By processing with import earlier existing SI will be replaced.
...
SI Import and subtasks
It’s possible export SI with subtasks however it is not possible to import SI with subtasks. Individual subtasks will be imported separately with issue type subtask.
...
After closing import window SI Table will be shown with main SI and additional SI with subtask issue type.
...
Subtasks - Omit subtasks
When choosing this option list of SIs will show only main SI, subtasks will not be displayed.
...
To import proceed to change name or skip duplicate or override duplicate.
SI Import and custom fields
For default fields during import each column will have a corresponding name to it. However custom fields will be displayed with their ID. For example customfield_10096.
...