Migrating Smart Checklist to Forge
- Oleksandr Haiun
- Julia Romanenkova
Smart Checklist is moving to Forge!
Overview
Smart Checklist is transitioning from Connect to Forge to align with Atlassian’s latest app development platform. This change enhances security, performance, and compliance but introduces some necessary adjustments for users.
Actions Required
👤 Custom Permissions: Custom permissions should be reconfigured within permission schemas.
Smart Checklist Permissions settings will be migrated without changes.
Project-level permissions will be reset post-migration. They must be manually reconfigured.
💡HINT: To simplify reconfiguration, we recommend taking a screenshot of your current project permissions setup before migration. This will serve as a reference when manually resetting permissions afterward. For detailed steps on configuring project permissions, refer to Permissions & Access
Before Migration | After Migration |
|---|---|
 Before Migration. |
☝🏼NOTE: Until custom permissions are reconfigured, users will not be able to see and work with checklists in issues. Please ensure that the permissions are properly set up to restore visibility.
🔄 Automation Rules: Any automation relying on entity properties will need to be updated to use custom fields.
Before Migration |
|
|---|---|
What Else You Need to Know
Uninstalling the Forge app will delete all checklist data.
Two new custom fields (Checklists and Smart Checklist Progress) will be added if not already present—these are required for the app to function.
Smart Checklist header will always be visible in JSM tickets on customer portal (pending Atlassian fix FRGE-1661).
Link rendering will be simplified.
Before Migration | After Migration |
|---|---|