Time in Status (Forge) for Jira CloudOverview
The Import / Export tab in the admin panel lets you:
- Export your configuration to a JSON file for backup or transfer to another Jira site
- Import a previously exported configuration, with options to handle conflicts
- Convert Data Center (Server) format configurations to Forge format during import
Export
Exportable sections
You can selectively export any combination of:
| Section | Description |
|---|---|
| Calendars | Work calendars with all settings |
| Custom Events | Custom event definitions |
| Field Settings | Time in Status field settings |
| Web Panels | Time in Status web panels |
| Stopwatch Field Settings | Stopwatch field settings |
| Stopwatch Web Panels | Stopwatch web panels |
| Timer Field Settings | Timer field settings |
| Timer Web Panels | Timer web panels |
| Time Between Dates Field Settings | TBD field settings |
| Calendar Field Configurations | Calendar Select field context configs |
How to export
- Open the admin panel > Import / Export tab
- Click Export
- Select the sections you want to export (or use Select All)
- Click Export
- The JSON output appears in a text area
You can:
- Copy to Clipboard - copy the JSON to paste elsewhere
- Download File - save as a
.jsonfile with a timestamped filename
Import
How to import
- Open the Import / Export tab
- Click Import
- Upload a JSON file or paste JSON content
- The app validates the file and shows a preview of what will be imported
- Select which items to import (checkboxes for each item)
- Choose a conflict strategy for items that already exist
- Click Import
- Review the results
Conflict strategies
When an imported item has the same name as an existing item:
| Strategy | Description |
|---|---|
| Skip | Keep the existing item unchanged. The imported item is ignored. |
| Overwrite | Replace the existing item with the imported version. |
| Rename | Import the item with a numeric suffix appended to avoid the conflict. For example, if a calendar named Business Hours already exists, the imported one is stored as Business Hours (1); if that also exists, Business Hours (2), and so on. |
Validation
Before importing, the app validates:
- Format - correct JSON structure and version
- References - items that reference other items (e.g., a field setting referencing a calendar) are checked for consistency
- Conflicts - items with matching names are flagged
Each item in the preview shows:
- Action: Create, Update, or Skip
- Warnings: any issues found during validation
- Valid: whether the item can be imported
Data Center format conversion
When you upload a JSON file exported from the Data Center (Server) version of Time in Status, the app automatically detects the format and converts it to Forge format.
The DC format (version 2) is converted to Forge format (version 1) with:
- Calendar mappings
- Field setting conversion
- Event trigger mapping
- Status and status category ID conversion
Note: some DC features may not have direct Forge equivalents. The app shows conversion warnings for any items that could not be fully converted.
File limits
| Limit | Value |
|---|---|
| Maximum file size | 5 MB |
| Format | JSON |
Use cases
Backup configuration
Export all sections periodically to have a backup of your configuration. Store the JSON file in your team’s document management system.
Transfer between Jira sites
- Export from the source Jira site
- Import into the target Jira site
- Use Rename strategy if both sites already have some configuration
Migrate from Data Center
- Export configuration from your DC instance (using the DC app’s export feature)
- Import the DC JSON file into the Forge app
- The app automatically converts the format
- Review conversion warnings and adjust as needed
- Bind field contexts to the imported settings
See Migration from Data Center for a complete guide.
Tips
- Export before changes: always export your current configuration before making significant changes. This gives you a restore point.
- Selective import: you do not need to import everything. Use the checkboxes to select only the items you need.
- Calendar references: if you import field settings that reference calendars, import the calendars first (or in the same batch) so the references resolve correctly.
- Review warnings: pay attention to validation warnings. They may indicate missing calendar references or unsupported features from DC format.
