Supported object types
On this page: |
Configuration only
If exporting or importing only the configuration of projects, the objects listed below can be handled. Links provide further information specific to some object types.
Global objects
Issue type
Issue type scheme
Custom field (including its configuration schemes)
Screen scheme
Screen
Issue type screen scheme
Field configuration
Event types
Status
Resolution
Priority
Priority schemes (since version 2.2.4)
Issue link types
Project role
Permission scheme
Notification scheme
Issue security scheme
Category
Project-specific objects
Members of project roles in the project
Service Management:
(since version 2.3.0)
Request types (including their fields, predefined values, and status mappings)
Request type groups
Queues
SLAs (including calendars, goals, and start/stop/pause conditions)
(since version 2.3.2)
Automation rules and Default event user
Notification rules
Approvals
(since version 2.3.4)
Portal settings (name, intro text, announcement, whether agents can manage announcements). Logos are not supported.
Email integration settings
Knowledge base integration
Customer satisfaction feedback survey configuration
Custom reports
(since version 2.3.8)
Customer permissions
Complete projects
If exporting or importing complete projects (i.e., their configuration, data, and attachments), the following object types will be handled in addition to the previous list of configuration objects:
Issues, including all their parts like:
Comments
Worklogs
Change history
Attachments
Any missing users that are referenced by the issue data being imported
Service Management:
Customer satisfaction feedback survey results (since version 2.3.5)
Organizations (since version 2.3.6)
Project Configurator uses Jira's built-in data import functionality to import your project data and is therefore subject to the restrictions described in Atlassian's Restoring a project from backup.
If you are importing complete projects, you should be aware of how your project data will be handled by reviewing the 'Preparing your target Jira instance' section of this article.