This article explains which data types ProBackup can restore for Jira and any known limitations.
Note: Jira restores always create new items. ProBackup never overwrites or changes existing data in Jira.
Projects
When you restore a project, a new project is created in your Jira site. It gets the original name followed by "(restored" and the restore date, and a new project key (the original key plus a few extra letters, because Jira does not allow two projects with the same key).
All issues of the project are restored into the new project, together with their comments, attachments and child issues.
Issues
When you restore an issue, a duplicate is created in the related project. The following data is included:
Summary, description, issue type and priority
Assignee, labels, due date and components
Most custom field values
Status: ProBackup moves the restored issue through your workflow to reach the original status, when your workflow allows it
Comments and attachments
Child issues
Known limitations:
The restored issue gets a new issue key.
Not all custom field values can be restored. Values that Jira rejects are skipped, and Sprint and Rank fields are never restored.
Components are re-attached only if they still exist in the project. Deleted components are not recreated.
Comments
When you restore a comment, a duplicate is created in the related issue.
Files
When you restore a file, it is added to the related issue.