SI Export/Import | Jira Automation Rules Import
Exporting Scheduled Issues
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 Scheduled Issue Actions. After clicking it a menu will appear with multiple options and one of them is Export to CSV that allows you to export current SIs and their subtasks to .csv file.
Before Scheduled Issues will be exported a pop up window will appear. In there you can choose fields to be exported with Scheduled Issues. You may even uncheck all fields leaving only required fields.
Some fields cannot be unchecked as they’re required to later Import Scheduled Issues.
Some fields when hovered over will display additional information on what happens if SI is exported without it.
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.
Method through Excel is advised to only use to view date for easier reading. Saved Scheduled Issues like that won’t be possible to import.
Export to .CSV can be used to create backups of Scheduled Issues.
Export to .CSV can be used to perform analytics in Excel.
Importing SIs
Exported SIs can be now imported through option Import Scheduled Issues from CSV located above SI table in Scheduled Issue Actions button.
By clicking Import Scheduled Issues from CSV button a small window pops up that allows to choose which .csv file to import.
When file is chosen the window will switch. Available SIs from file will be displayed with all fields and values.
By clicking Import SIs will be imported. Window pop up will switch to display if operation was a success and after closing it SI Table will contain imported SIs.
There are few things that can be used during import. They’ll be explained now.
SI Import and timezone
After choosing a file on the top of the table there is written current timezone. You can import SIs in different timezone by choosing one from the list.
By clicking on the name of current timezone list of available timezones will be displayed.
Here for example we’ll go with Europe/London.
After import SI Table will contain SI that will execute in different timezone as well as other fields will be adjusted to chosen timezone.
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 - Name change
Click on the name of marked SI and type in a new name.
Type in a new name and click on checkmark on anywhere on the pop up and the name will change.
Duplicates - Skip duplicates
Here we’ll Skip duplicates. By choosing this option duplicated SIs will be deselected.
After importing only the selected SI will be imported.
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 to export SI with subtasks. Scheduled Issue will be imported with its subtasks as long as siId field wasn’t disabled in export.
If siId field is disabled during export then subtasks attached to SI will be imported as separate SIs with issue type subtask.
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.
Jira Automation Rules
In Scheduler you can import .JSON files of Jira Automation Rules. Go to System → Global automation. Choose a rules tab and in there create a rule.
Return to rules and you can export all created rules or individual rules
Now in Scheduler after obtaining .JSON file with exported rule click on Scheduled Issue Actions → Import Jira Automation rules from JSON.
Select JSON file and Jira Automation Rule will be imported as Scheduled Issue
When: must be a Scheduled trigger. Other rules with different triggers will be added in future updates.
Action: must be Create Issue. In the future more options will be added.
If there are multiple Create Issue only one will be used. In the future it will be expanded
Basic Scheduled trigger will be converted to Schedulers Interval/Cron trigger
More frequent triggers like 1h will be converted to Schedulers Interval/Advanced Cron equivalent of running every 1 hour
Importing disabled rule will be imported as inactive Scheduled Issue
Feel free to tell us what topic should be covered: thescheduler@psc-software.atlassian.net