Import/Export configuration

Dynamic Forms lets you export and import rule configurations with ease - reuse them across projects or transfer them to another Jira instance instead of setting them up from scratch.

You can import and export the configuration of a rule set in all space types. Import and export are available in the rule set editor.

Export configuration

Steps

1. Go to Space settings > Apps > Dynamic Forms.
2. Click Configure rules on the rule set card.
3. Click … in the header.
4. Click Export.

Result

The configuration file is saved to your computer as a JSON file.

Import configuration

Steps

1. Go to Space settings > Apps > Dynamic Forms.
2. Click Configure rules on the rule set card.
3. Click … in the header.
4. Click Import.
5. Drop a JSON file with the configuration or click Browse to find the file on your computer.
6. Check the field mapping in the Import configuration dialog. See Mapping summary.
7. In Import type, choose:
   • Replace fields - updates only the imported fields.
   • Replace configuration - overwrites the entire configuration of the rule set within the available fields.
8. Click Import configuration.

9. The imported configuration is a draft. Click Apply changes to save it, or Discard to cancel it.

Result

The configuration is imported to the rule set.

Importing and exporting between Jira instances

Use the import and export feature to transfer Dynamic Forms rule configurations from one Jira Cloud instance to another - for example, to replicate a tested configuration to a production instance or share rules with another team.

To transfer a configuration, export it from the source instance and import it into the target instance. The steps are the same as for within-instance import and export described above.

When you import a file from a different Jira instance, Dynamic Forms tries to match each field in the exported configuration to a field on the target instance - first by field ID, then by name.

Mapping summary

After you upload the JSON file, the Import configuration dialog shows a mapping summary. When all fields are matched, All fields have been mapped successfully is displayed.

• The Imported field column lists fields from the exported file.
• The Linked field column shows the matching field in your Jira instance, or Not set if no match was found.
• The Imported File Preview panel on the right shows the number of rules found in the file, all rules, and any warnings.

What happens to unmapped fields

When some fields from the exported file are not found on the target instance, Dynamic Forms shows a warning banner before you confirm the import.

The behavior depends on where the unmatched field appears:

• Parent fields without a match (main fields with rules) - silently skipped. Their rules are not imported.
• Fields used inside conditions or actions without a match - imported with a warning marker. You can complete the rules after the import.
• Options inside conditions or actions without a match - imported with a warning marker.

After reviewing the mapping, choose the import type and click Import configuration. The configuration is loaded in draft mode - click Apply changes to save it or Discard to remove it.