Restore Status Code

Category: Failed to create work items while restoring it

Reason:

1. Revyz internal issue: Failure could be due to one of the following reasons:

   1. Missing Required Fields:
      This occurs when older work items lack data for fields that were recently marked as mandatory (via workflow transitions or configuration updates). These items will fail validation during creation as the work items have no values against the mandatory fields.

   2. Atlassian API failure:
      Failures caused by API rate limits, structural constraints, or temporary transient errors.

2. Resolution:

1. Missing Required Fields: Temporarily change the configuration on the destination site to remove the mandatory field requirement and trigger a new restore.

2. Atlassian API failure: Reach out to Revyz support.

Category: Work item has been created successfully, however, failed to update a value for a certain field.

Reason: Field values for work items may fail to set due to:

• Invalid user: The specified user (such as for the field reporter or any other user field) is deactivated, suspended, or missing from the site.

• Atlassian API errors: Failures stemming from rate limits, structural constraints, or transient network issues.

Resolution:
Following actions are recommended based on the reasons of failure:

1. Invalid: Ensure all users are present and active on the site and trigger another restore.

2. Atlassian API failure: Reach out to Revyz support.

Category: Failed to create sub-task

Reason: Failed to create sub-task independently.

For example, the user selected a sub-task work item to restore, but its parent work item is
missing. In such cases, the sub-task cannot be created independent.

Resolution: Select both the parent work item and the sub-task work item to restore.

Category: Restoring the work-items failed to update the status.

Reason: Failed to Restore Work Item Status

Revyz cannot restore work item status if validations or post-functions are required during work item transition. Workflow status restrictions may require user intervention during work item transition, depending on the configuration.

Resolution: User should follow these steps:

• Navigate to Revyz Jobs → Restore jobs

• Select the restore job ID

• Select the “Post actions“ tab

  • Download the JQL file, which provides a filter to bulk edit and transition work items to their statuses.

Category: Create Issue

Reason: Failure setting intended status of restored issue either due to workflow restrictions or Jira API limitations

Resolution: Check 'Post actions' in job details to fix it

Category: While restoring a work item failed to add a comment.

Reason: Failures from Atlassian API rate limits, structural constraints, or temporary errors can cause comment creation to fail.

Resolution: Customer is advised to check the restore logs. If they can fix an Atlassian error, resolve it and retry the restore. Otherwise, contact Revyz support.

Category: While restoring a work item, failed to add attachment (s).

Reason: Restoring an attachment can fail for these reasons:

• Attachment size exceeds the allowed limit

• Attachment creation can fail due to Atlassian API rate limits, structural constraints, or temporary errors.

Resolution: We recommend following actions based on the reasons of failure:

Attachment size exceeds limit: Increase the attachment size in the site global settings and retry
work item restore.

Atlassian API failure: Reach out to Revyz support.

Category: Failed to add worklogs while restoring a work item

Reason: Worklogs creation can fail due to Atlassian API rate limits, structural constraints, temporary errors or worklogs limit

Resolution: Recommended to contact Revyz support.

Category: Failed to add original work item backed up data as an JSON attachment.

Reason: Revyz adds original backup work item as an attachment to restored issue, so that user can have original copy with them. It can be used for:

• Work item history

• Reconciling missing field values

Reason for failure;

• Atlassian API failure

• Revyz internal issue

Resolution: Recommended to contact Revyz support.

Category: Failed to add original work item backed up data in the form of CSV as an attachment

Reason: Failed to add original work item backup data as CSV attachment

Revyz attaches the original backed-up work item to the restored issue, ensuring users always have access to the original copy.

It can be used for following purpose:

1. Work item history

2. Reconcile missing field values

Reason of failure:

1. Atlassian API failure

2. Revyz internal issue

Resolution: Recommended to contact Revyz support.

Category: Issue_worklog_partial

Reason: Failure restoring one of the worklogs.

Resolution: Check logs. Collect information about cause if available and share it with Revyz.

Category: Failed to add Work item links

Reason: Revyz might fail to link work items due to one of the following scenarios:

• Linked work item is not present or might’ve been deleted.

• Linked work item was not selected for restore and is not present on the site.

• Atlassian API rate limits, structural constraints or temporary errors

Resolution: We recommend following actions based on the reasons of failure:

• Missing linked work items: Select the linked work items as well for restore in the same restore job.

• Atlassian API failure: Reach out to Revyz support.

Category: Failed to add a comment to the restored work item on behalf of the original author.

Reason: If the user who added the comment is absent, deactivated, suspended, or deleted, impersonating them to add a work item comment in the restored work item will fail.

Resolution: No action required.

Category: Issue_Comments_Connect_App_User

Reason: The issue comment was restored using the Connect app user as an error occurred while attempting to restore.

Resolution: The comment with the original comment owner.

Category: Issue_worklog_deactivated_user

Reason: Issue worklog restored with connect app user as deactivated user.

Resolution: Check logs. Collect information about cause if available and share it with Revyz.

Category: Issue_worklog_connect_app_user

Reason: The issue worklog was restored using the Connect app user as an error occurred while attempting to restore.

Resolution: The worklog with the original comment owner.

Category: Failed to upload the original work item history as a CSV attachment to the restored work item.

Reason: Atlassian API rate limits, structural constraints or temporary errors

Resolution: Contact Revyz support

Category: Failed to upload the original work item worklogs as a CSV attachment to the restored work item

Reason: Atlassian API rate limits, structural constraints, or temporary errors

Resolution: Contact Revyz support

Category: Failed to update a work item

Reason: When updating a work item, the API fails. It could fail due to one of the following reasons:

• A field custom might be mandatory as per the latest configurations.

• Atlassian API rate limits, structural constraints or temporary errors

Resolution: Contact Revyz support.

Category: Failed to update a work item

Reason: When updating a work item, the API fails. It could fail due to one of the following reasons:

• A field custom might be mandatory as per the latest configurations.

• Atlassian API rate limits, structural constraints or temporary errors

Resolution: Contact Revyz support

Category: Failed to add Work item links

Reason:

When restoring a work item, the associated work items are also linked. However, the associated work items may fail to be linked to the restored work item, if:

• Linked work item is not present or might've been deleted.

• Linked work item was not selected for restore and is not present on the site.

• Atlassian API rate limits, structural constraints or temporary errors

Resolution:

Following actions are recommended on the basis of reasons of failure:

• Missing linked work items: Select the linked work items as well for restore in the same restore job.

• Atlassian API failure: Reach out to Revyz support.

Category: Issue_link_partial

Reason: Failed to recreate one of the original issue links in the restored issue.

Resolution: Check logs. Collect information about cause if available and share it with Revyz.

Category: Workflows

Reason: Failed to restore the workflow contains validators, post-functions can be skipped based on various conditions

Resolution: Contact Revyz support.

Category: Workflows

Reason: Failed to restore sub-configurations of the workflow

Resolution: Check restore job logs from job details.

Category: Workflow_Child_Skip

Reason: If a workflow is currently active, Revyz may be unable to overwrite it. To prevent conflicts, a new version will be created using the naming convention: <workflow name>_revyz<Restore job ID>.

Resolution:

1. Rename the Original: Rename the existing workflow (e.g., "Workflow_OLD").

2. Rename the Restored: Strip the restoration metadata from the new workflow:

   • Change <workflow name>_revyz<Restore job ID> back to the original <workflow name>.

3. Reassign Projects: Update project settings to associate the original projects with the newly restored workflow.

Category: Workflow_Create_For_Update

Reason: Revyz cannot modify active workflows. Instead, it creates a unique copy using the format: <workflow name>_revyz<Restore job ID>. <workflow name>_revyz<Restore job ID>.

Resolution:

1. Rename the Original: Rename the existing workflow (e.g., "Workflow_OLD").

2. Rename the Restored: Strip the restoration metadata from the new workflow:

   • Change <workflow name>_revyz<Restore job ID> back to the original <workflow name>.

3. Reassign Projects: Update project settings to associate the original projects with the newly restored workflow.

Resolution: Check restore job logs from job details.

Category: Create_Workflow

Reason: Removing extra spaces in workflow name. After removing spaces, if workflow with same name is present on destination then workflow creation fails

Resolution: Check restore job logs from job details.

Category: Screens

Reason: Failed to restore the screen

Resolution: Contact Revyz support.

Category: Screen

Reason: Failed to restore sub-configurations of the screen

Resolution: Check restore job logs from job details.

Category: Screen tab

Reason: Locked fields can't added/associated in the screen tab if it is not available on destination site. Locked fields are not meant to be created or modified in that way due to Atlassian API limitation.

Category: Filters

Reason: Failed to restore the filter

Resolution: Contact Revyz support.

Category: Filters

Reason: Failed to restore sub-configurations of the filter

Resolution: Check restore job logs from job details.

Category: Sub-task Issue type

Reason: Sub task issue type failed as subtasks are disabled on destination site

Resolution: Check restore job logs from job details.

Category: Issue type scheme restore

Reason: Issue type scheme creation failed.

Resolution: Check restore job logs from job details.

Category: Issue type

Reason: Issue type creation failed.

Resolution: Check restore job logs from job details.

Category: Issue type avatar

Reason: Issue type avatar creation failed.

Resolution: Check restore job logs from job details.

Category: Epic_issue type

Reason: Issue type of epic creation failed due to Jira restrictions.

Resolution: Check restore job logs from job details.

Category: Issue_type_update

Reason: Failed to update issue type (Description).

Resolution: Check restore job logs from job details.

Category: Issue_type_scheme_update

Reason: Can't remove an issue type assigned to issues. This is expected behavior according to Jira.

Resolution: Check restore job logs from job details.

Category: Field context

Reason: Creating field context failed as context has one project A is used in another context on destination site

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Creating field configuration scheme failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Restoring field configuration failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Restoring field configuration items failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Creating field failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Creating field context failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Restoring field context options failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Creating field due to Jira restrictions failed

Resolution: Check restore job logs from job details.

Category: Field configuration scheme

Reason: Creating field due to Jira restrictions (Locked field) failed

Resolution: Check restore job logs from job details.

Category: Issue type screen scheme

Reason: Creating issue type screen scheme failed

Resolution: Check restore job logs from job details.

Category: Issue type screen scheme

Reason: Creating screen scheme failed

Resolution: Check restore job logs from job details.

Category: Issue type screen scheme

Reason: Creating screen failed

Resolution: Check restore job logs from job details.

Category: Issue type screen scheme

Reason: Creating screen tab failed

Resolution: Check restore job logs from job details.

Category: Workflow scheme

Reason: Creating workflow scheme failed

Resolution: Check restore job logs from job details.

Category: Workflow scheme

Reason: Creating workflow failed

Resolution: Check restore job logs from job details.

Category: Workflow scheme

Reason: Restoring workflow rule failed

Resolution: Check restore job logs from job details.

Category: Security (PERMISSION_SCHEME_FAIL 001)

Reason: Creating permission scheme failed

Resolution: Check restore job logs from job details.

Category: Permission scheme Creation for Update

Reason: Creating permission scheme in case of modify scenario, because updating permission scheme involves updating permissions given to the users/groups/project roles etc... This may lead to security problems.

Resolution: Check restore job logs from job details.

Category: Security (PROJECT_ROLE_FAIL 002)

Reason: Creating project role failed

Resolution: Check restore job logs from job details.

Category: Permission scheme Creation for Update

Reason: Creating permission scheme in case of modify scenario, because updating permission scheme involves updating permissions given to the users/groups/project roles etc... This may lead to security problems.

Resolution: Check restore job logs from job details.

Category: Project (PROJECT_FAIL 001)

Reason: Project creation failed

Resolution: Check restore job logs from job details.

Category: Project (PROJECT_CATEGORY 002)

Reason: Creating project category failed

Resolution: Check restore job logs from job details.

Category: Project (PROJECT_FEATURE 003)

Reason: Creating project feature failed

Resolution: Check restore job logs from job details.

Category: Project (PROJECT_FEATURE_EXCLUDED 005)

Reason: Creating project feature due to Jira restrictions failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (COMPONENTS 001)

Reason: Creating project component failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (COMPONENTS_LEAD 010)

Reason: Restoring component lead possibly due to unavailability of the user on tenant failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (VERSIONS 002)

Reason: Creating project version failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (BOARDS 003)

Reason: Creating board failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (SPRINTS 004)

Reason: Creating Sprint failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (FILTERS 007)

Reason: Creating Filter failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (FILTERS_PARTIAL 008)

Reason: Creating Filter partial failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (FILTERS_SETTINGS 009)

Reason: Creating filter due to user permissions failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (FILTERS_SETTINGS 009)

Reason: Creating filter due to user permissions failed

Resolution: Check restore job logs from job details.

Category: Miscellaneous (UNCHECKED_BY_USER 010)

Reason: Excluded by user

Resolution: Check restore job logs from job details.

Category: Object schema

Reason: Object schema creation failed

Resolution: Check restore job logs from job details.

Category: Object schema

Reason: Object schema creation failed

Resolution: Read only object schema is not supported for restore as they are not editable.

Category: Object Types

Reason: Object type creation failed

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type position failed

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type attribute failed

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type attribute - Reserve attribute failed

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type attribute - Unable to find parent object type

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type attribute - Unique name is required

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type attribute - Cross schema relation disabled

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Impossible to set child's attribute as label if inheritance is enabled for parent

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Invalid reference type (if original reference type is deleted)

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type is restored as <object type>_revyz<JobID> if an object type with original name is already present.

Resolution: Check restore job logs from job details.

Category: Object Types

Reason: Object type icon is not restored

Resolution: Object type is restored with alternate icon

Category: Statuses

Reason: Creating status failed

Resolution: Check restore job logs from job details.

Category: Statuses

Reason: Status with same name is failed to restore

Resolution: Status with same name was already present hence status is created adding 'revyz<jobId>' as suffix

Category: Reference types

Reason: Reference types with same name is failed to restore

Resolution: Reference types with same name was already present hence reference types is created adding 'revyz<jobId>' as suffix

Category: Attributes

Reason: Attribute with default reference type

Resolution: Attribute is restored with default reference type

Category: Attributes

Reason: Attribute is not updated

Resolution: Could not edit the attribute as it is not editable

Category: Attributes

Reason: Attribute create without attribute type 'Group'

Resolution: Attribute is created without type group

Category: Attribute Label

Reason: Failed to Update label

Resolution: Check restore job logs from job details.

Category: Assets objects

Reason: Object creation failure

Resolution: Check restore job logs from job details.

Category: Assets objects

Reason: Failed to add value to object attribute

Resolution: Check restore job logs from job details.