Why are there warnings?

Missing Global or Project template(s) after migration

This issue can occur if the original template:

• Had no checklist items(no data loss, but warning is expected)

• Was deleted (no data loss, but warning is expected)

• Was not properly created in the Connect app

• Encountered an unhandled error during backup

• Had missing or corrupt metadata

As a result, the template is skipped during migration.

The expected template is missing from the global or project template list.

Global Templates message:

Failed to get backup data for global template 1000.

Project Templates message:

Failed to get backup data for project 10223 template 14324

Or

No template metadata found for project 12334 template 10223. This is common for deleted templates, importing skipped.

For Global Templates:

1. Note the missing template ID from logs.

2. Share the ID with the support team to check whether recovery is possible.

For Project Templates:

1. Identify the project and template ID from the logs.

2. Open the project properties:
   https://<instance-url>/rest/api/3/project/<projectId>/properties

3. Look for entries like:

   • com.railsware.SmartChecklist.templateId.<templateId>

   • com.railsware.SmartChecklist.templateMeta.<templateId>

4. If checklist content or metadata is missing, and the template is expected, contact support with the template ID.

Checklist for the issue was not restored from the data backup.

This is a generic warning that occurs when the app failed to restore a checklist for an issue during migration.
It typically points to an unhandled error on the Forge side during import.
The exact cause varies and is usually found in the Details field of the warning message.

Checklist is missing in the issue view.

Message:

Checklist for the issue 10006 was not restored

May include additional context in the Details field.

1. Identify the affected issueId from the logs (e.g., 10006).

2. Check the issue properties:
   https://<instance-url>/rest/api/2/issue/10006/properties

3. Then inspect the checklist property directly:
   https://<instance-url>/rest/api/2/issue/10006/properties/com.railsware.SmartChecklist.checklist

If the property exists and contains data, but the checklist is empty in the UI, this indicates a failure during checklist restoration.

Please contact support for further investigation.

Checklist for the issue was not added to the backup properly.

Checklist data was not properly prepared for migration by the Connect app.
Possible reasons include:

• Misconfigured custom fields (e.g. missing or limited context)

• Workflow conditions or post-functions preventing issue edits

• App lacking required permissions at the time of backup preparation

Since no data was exported, the Forge app had nothing to import. This results in empty checklists after migration.
Data for migration was not properly created by connect app.

Checklist is missing in the issue view.

None - this case typically does not produce errors in logs.

1. Find an issue where the checklist is expected but missing.

2. Open issue properties:
   https://<instance-url>/rest/api/2/issue/<issueId>/properties

3. Look for checklist-related properties:

   • com.railsware.SmartChecklist.checklist

   • com.railsware.SmartChecklist.historyBackup.<timestamp>

If both the properties and the checklist UI are missing, the issue was likely not backed up properly before migration.
Please contact support for further investigation.

Missing checklist history for issues migrated from DC/Server

The migration from Server/DC to Cloud does not include checklist history, so these issues have no historical checklist data. When the Forge app tries to load history, a warning is triggered. No data loss, but warning is expected.

Message:

No history events found for issue 313833. This is expected for the tickets that were migrated from Server/DC.

1. Open in your browser:
   https://<instance-url>/rest/api/2/issue/<issueId>

2. Find the issue key.

3. Confirm that the issue was migrated from DC/Server.

4. Verify that no changes were made to the checklist in Cloud after migration.

If the issue originated from DC/Server, this behavior is expected.

Checklist history for cloned issues

If a third-party app like Deep Clone is used to copy issues, it duplicates the checklist history properties from the original issue. Since the new issue has a different ID, the Forge app skips restoring history during migration, resulting in a warning.
Checklist content and history is not lost - only history restoration results in warning due to the ID mismatch.

The checklist history appears as expected.

Message:

Issue ID mismatch while restoring history backups, skipping event

"issueId": "311245",
"eventIssueId": "278943"

From the logs, identify both issueId and eventIssueId.
For both IDs:

1. Open in your browser:
   https://<instance-url>/rest/api/2/issue/<issueId>
https://<instance-url>/rest/api/2/issue/<eventIssueId>

2. Find the issue keys to check how they are related.
   Usually, eventIssueId refers to the original (cloned) issue where the history backup properties were copied from.

Warnings due to history size

Due to Forge storage size limitations, checklists and history events exceeding 245,760 characters can’t be saved in Forge storage. Such history events are still shown in the History tab, but are pulled from the issue property, not from the Forge storage. No data loss, but warning is expected.

Note: There may also be other unhandled cases where saving to storage fails - check the Details field in the warning for the reason.

Checklist history is displayed correctly in the UI.

Message:
"Failed to restore event id \"1740679313076\" for issue id \"10150\"

Details:
"Error: \n Event content size is too big: 564709, should be less than 245760\n Skipping saving event with id: 1740679313076"

1. From the logs, identify the issueId mentioned in the warning.

2. Open in your browser:
   https://<instance-url>/rest/api/2/issue/<issueId>

3. Find the issue key and inspect the checklist and history section to confirm whether history events are properly listed.

Checklist history was not restored properly from the data backup.

The Forge app found a valid checklist history backup property, but failed to read or restore it.
This may be due to issues with decoding, unzipping, or other internal errors when accessing the stored backup.

History may be partially displayed or may be missing entirely, depending on which events failed to restore.

Message:
Unable to restore history event 1738876118323 for issue 10006.
Details :
Error: error:1C800064:Provider routines::bad decrypt

1. From the logs, identify the issueId mentioned in the warning.

2. Open in your browser:
   https://<instance-url>/rest/api/2/issue/<issueId>

3. Check the Checklist and History tabs in the issue UI
   → Confirm whether history is fully displayed

4. Open the issue properties:
   https://<instance-url>/rest/api/2/issue/10006/properties
   → Look for: com.railsware.SmartChecklist.historyBackup.<timestamp>

If the property exists but history is not displayed, it may indicate a data corruption or decryption issue.

Please contact support for further investigation.

Checklist history was not restored due to unknown reason.

This is a generic fallback warning triggered when the app fails to restore all history events for a given issue, but the root cause doesn't match any known error patterns (e.g. size limits, decoding issues, ID mismatches).
It typically indicates that something unexpected happened during the history restoration process.

Checklist may be present, but some or all history entries may be missing in the history tab.

Message:
History events for issue 10006 were not fully restored

1. From the logs, identify the issueId mentioned in the warning.

2. Open in your browser:
   https://<instance-url>/rest/api/2/issue/<issueId>

   • Find the issue key and inspect the checklist and history section to confirm whether history events are properly listed.

3. If the issue contains important data and the history is missing, please contact support for further investigation.