- Export Configurations
- Import Configurations
- Import Limits
- JSON Format Reference
- CSV Format Reference
- Validation Details
- Migration Between Instances
- Duplicate Configuration
- Bulk Enable/Disable
- Configuration Management
- Settings from Connect
- Next Steps
Export Configurations
Save configurations as JSON file:
- Go to Apps → Display Linked Issues settings
- Click Bulk Operations tab
- Select configurations to export
- Click Export Selected or Export All
The exported file contains all selected panel configurations and custom field configurations in JSON format.
Tip: Export configurations before making major changes as a backup.
Import Configurations
Load configurations from JSON or CSV file:

- Go to Bulk Operations tab
- Click Import
- Choose file format (JSON or CSV)
- Paste file content
- Click Validate to review
- Confirm import
Note: Imported configurations with duplicate names will be renamed automatically.
Note: Export and import includes custom field configurations alongside panel configurations.
Empty cells in CSV
In a CSV file an empty cell of a true/false column means “not set” and imports the way the configuration form shows an unset value: isEnabled, isShowName, isShowDescription and isShowCount import as true. Write false to turn them off.
Import Limits
Imports enforce the following limits:
| Limit | Value |
|---|---|
| Max configurations per import | 200 |
| Max file size | 10 MB |
| Max CSV rows (excluding header) | 1000 |
Imports exceeding these limits are rejected during validation.
JSON Format Reference
The JSON export wraps configurations in a package with metadata. Each configuration is a flat object - all fields live at the top level (no nested groups).
{
"metadata": {
"version": "1.0.0",
"exportedAt": 1715000000000,
"totalConfigs": 1
},
"configs": [
{
"name": "Open bugs in this project",
"description": "Shows open bugs for the current project",
"linkType": "JQL",
"jql": "project = {{ issue.fields.project.id | jqlRaw }} AND issuetype = Bug AND statusCategory != Done",
"linkedIssuesFieldId": [],
"linkTypes": [],
"displayFieldIds": ["summary", "status", "assignee"],
"fieldsMetadata": {},
"projects": ["PROJ1", "PROJ2"],
"issueTypes": ["Bug", "Story"],
"displayJql": "",
"displayModule": "jira:issuePanel",
"weight": 100,
"isEnabled": true,
"isShowName": true,
"isShowDescription": true,
"isShowCount": true,
"isShowJqlLink": false,
"rowsPerPage": 10,
"maxIssues": 50
}
]
}
Key Fields
| Field | Description |
|---|---|
name |
Configuration name (max 250 characters) |
description |
Free-form description |
linkType |
"EMPTY", "JQL", or "LINKED_ISSUES" - source of issues for the panel |
jql |
JQL query (when linkType is "JQL") |
linkedIssuesFieldId |
Field IDs for issues link source (when linkType is "LINKED_ISSUES") |
linkTypes |
Array of { id, name, direction, directionName } objects (when linkType is "LINKED_ISSUES") |
displayFieldIds |
Field IDs to display in the panel table |
fieldsMetadata |
Object keyed by field ID with rendering metadata |
projects, issueTypes |
Context filters - empty array means “all” |
displayJql |
Additional JQL gating panel visibility on the current issue |
displayModule |
Surface where the panel appears (see Modules) |
weight |
Display order: 0..1000, lower appears earlier |
isEnabled |
true to activate the configuration |
isShowName, isShowDescription, isShowCount, isShowJqlLink |
Toggle visibility of panel header elements |
rowsPerPage |
Rows per page (1-100) |
maxIssues |
Maximum issues to load (1-1000) |
Note: Exports may also include
_isGlobal: truefor global configurations (no project filter). This marker is read-only - it appears in exports but is ignored on import.
Tip: Generate a working JSON template by exporting a single real configuration from your instance, then edit it. This is more reliable than writing from scratch.
CSV Format Reference
The CSV export uses semicolon (;) as the column delimiter. Each row is one configuration.
Value encoding
| Value type | Encoding |
|---|---|
Simple string array (e.g., projects, issueTypes, displayFieldIds) |
Values joined with pipe | - e.g., PROJ1|PROJ2 |
Complex array or object (e.g., linkTypes, fieldsMetadata) |
JSON string inside the cell - quoted if it contains ; |
| Boolean | true or false |
| Number | Plain digits |
| Empty / null | Empty string |
Columns
The CSV export has one column per configuration setting. The main columns:
| Column | Description |
|---|---|
name |
Configuration name (max 250 characters) |
description |
Free-form description |
linkType |
EMPTY, JQL, LINKED_ISSUES |
jql |
JQL query (when linkType is JQL) |
linkedIssuesFieldId |
Pipe-joined field IDs |
linkTypes |
JSON array of { id, name, direction, directionName } |
displayFieldIds |
Pipe-joined field IDs |
fieldsMetadata |
JSON object keyed by field ID |
projects |
Pipe-joined project keys |
issueTypes |
Pipe-joined issue type names |
displayJql |
Display JQL (max 1000 characters) |
displayModule |
Surface identifier |
weight |
0..1000 |
isEnabled |
true / false |
isShowName |
true / false |
isShowDescription |
true / false |
isShowCount |
true / false |
isShowJqlLink |
true / false |
rowsPerPage |
1-100 |
maxIssues |
1-1000 |
_isGlobal |
Read-only on import - present in exports for global configs, ignored when importing |
Note: CSV is convenient for bulk review and spreadsheet editing. For full fidelity (including custom-field-specific fields like
customFieldIdandcustomFieldContextId), use JSON.
Validation Details
When importing configurations, the Validate step checks:
| Check | Description |
|---|---|
| Name uniqueness | Detects duplicate names across existing and imported configurations |
| Required fields | Ensures name and module are present |
| Module validity | Checks that the module identifier is valid |
| JQL syntax | Basic JQL syntax validation (if applicable) |
| Field limits | Validates field counts don’t exceed limits |
| JSON structure | Validates the JSON/CSV structure is well-formed |
Name Conflict Resolution
When an imported configuration has the same name as an existing one:
- The import tool flags the conflict during validation
- You can choose to rename the imported configuration (a suffix is added automatically)
- Existing configurations are never overwritten during import
Migration Between Instances
Use export/import to migrate configurations between Jira instances (e.g., dev → staging → production).
Migration Workflow
- Export all configurations from the source instance
- Review the exported JSON for environment-specific values:
- Project keys - must match on the target instance
- Issue type names - must match on the target instance
- Custom field IDs - may differ between instances
- Edit the JSON if needed to adjust values for the target environment
- Import into the target instance
- Validate and review the import preview
- Test imported configurations with real issues
Tips for Migration
- Project keys: Keep project keys consistent across environments when possible
- Custom fields: Use field names instead of IDs in templates when possible - names are more portable
- JQL queries: Review parametric JQL for environment-specific references
- Module settings: Module enable/disable settings are not included in export - configure these separately on each instance
Duplicate Configuration
Create a copy of existing configuration:
- Click … menu on the configuration row
- Select Duplicate
- New configuration created with “(Copy)” suffix
Bulk Enable/Disable
Enable or disable multiple configurations at once:
- Go to Bulk Operations tab
- Select configurations using checkboxes
- Click Enable Selected or Disable Selected
This is useful for:
- Temporarily disabling all panels during maintenance
- Enabling a set of new configurations together
- Testing by toggling configurations on/off
Note: Bulk enable/disable operations also apply to custom field configurations.
Tip: You can also toggle individual configurations using the switch in the configuration list.
Configuration Management
Edit
- Click on configuration name or row
- Modify settings
- Click Save
Delete
Remove configuration permanently:
- Click … menu
- Select Delete
- Confirm deletion
Warning: Deletion is permanent. Export configuration first if you may need it later.
Settings from Connect
The Settings from Connect block on the Bulk Operations tab shows the transfer of the Connect edition’s settings to this Forge edition:
- whether settings of the Connect edition were found on the site;
- when they were imported;
- how many configurations were created, skipped or created disabled, and what to check.
Import again re-runs the transfer and still skips configurations whose name already exists. When no settings were found, paste the transfer file of the Connect edition into the block and select Import from Connect file. Only a Jira administrator can do this.
See Moving from the Connect edition for what is transferred and what to check afterwards.
Next Steps
- Configuration Basics - Basic panel settings
- Testing Panels - Preview and debug configurations
- Templates - Dynamic content syntax
- Moving from the Connect edition - Settings from Connect
- Limits - Configuration size and count limits

