Migration to Forge (Release Note)
- Wissal Ouerghi
- salah.khamassi
This version is being rolled out gradually with the assistance of the Atlassian team. Please check for the update's availability over the next few days.
1. Introduction
As part of our continuous improvement and alignment with Atlassian’s Cloud-first strategy, Timesheet Tracking for Jira has been successfully migrated to Forge, Atlassian’s next-generation cloud development platform.
This major step offers:
Improved security thanks to Forge’s sandboxed environment.
Optimized performance and scalability.
Full compliance with Atlassian’s cloud ecosystem and future direction.
2. Automatically Migrated
The following configurations and data have been automatically migrated to the Forge version:
Access & Configuration
Access Control:( Administration > Access) All user and group permissions (as defined in the Access tab) are retained.
Capabilities Settings ( Administration > Capabilities):
Timer enablement and related restrictions.
Project Overview and linked projects.
AI Features toggle: Whether AI-based work description suggestions are enabled.
Planning features toggle.
External calendar integrations (Google, Microsoft).
Issue context view (Beta).
Prefernces : All user preferences defined under the General settings page are retained, including:
Initial module view (Reports)
Bypass issue limits
Auto-load of the last used filter
Time display settings
Export format preferences
First day of the week
Working hours and workweek range
Event card display options
Data & Usage
Saved Filters: All filters saved in all views.
User Timers: Active timers at the moment of migration.
Workplans: Including recurring schedules and date ranges.
Suggestions List : Timesheet, Calendar , planning
These components will be fully functional in the new Forge-based interface.
3. Not Migrated — Manual Reconfiguration Required
Due to platform limitations, the following elements cannot be retained and will need to be manually reconfigured by users.
Once this step is completed, the feature will function as it did in the previous version, with the last state preserved.
A. Dashboard Gadgets configurations :
All existing Timesheet gadgets added to Jira dashboards will be visible, but with a warning regarding the Licence.
Users will need to manually reconfigure the Dashboard gadgets.
B. Grid States in Application Modules
Grid configurations (columns, sorting, filters, etc.) are not preserved in the following modules:
Timeline
Timesheet
Planning
Users will need to manually reconfigure their preferred layout and filters post-migration.
C. Calendar View Preferences
Two specific UI preferences in the Calendar module are reset:
Zoom Level: Custom zoom states are lost.
Order By: Preferred sorting ( "Started", "Duration", "Created") is reset to default.
Show/Hide Events: This visibility toggle setting is not retained and must be manually set again after migration.
4. Recommendations for a Smooth Transition
Before Migration
Take screenshots of current gadgets, custom views, and calendar preferences.
Notify teams to save any unsaved data and note down key preferences.
After Migration
Access the app via Jira → Apps → Timesheet.
Re-add and reconfigure any dashboard gadgets.
Readjust module-specific settings (grid columns, filters, calendar zoom/order).
5. Support & Assistance
We are here to help make your transition smooth and efficient. For any migration-related inquiries or support:
Email: info@cappsule.io
Portail : https://cappsule.atlassian.net/servicedesk/customer/portal/5
6. How to Update
Please visit the Atlassian official Update procedure here
Thank you for your continued trust in our addon.