Timepiece - Time in Status for Jira has officially migrated from Atlassian Connect to Atlassian Forge. Because of this architectural upgrade, Jira administrators are required to perform a manual update to approve new permission scopes. This guide explains what the Forge migration means for your Jira instance, why you are seeing new permission requests, and exactly how to update the application to prevent any disruption to your reporting workflows.
If you are new to Timepiece, it is a process intelligence solution that turns raw Jira history into actionable insights by generating time tracking reports directly from issue history. As one of the oldest and most advanced tools of its kind on the Atlassian Marketplace, it is trusted by over 2 million users across 4,500 companies in 110 countries.
The application helps various roles optimize their workflows based on objective data:
Project and Product Managers: Gain visibility into where work is stuck, allowing for precise Cycle Time measurement to deliver projects on schedule and budget.
Scrum Masters and Agile Coaches: Use the data to find concrete evidence of process breakdowns (such as extended "Code Review" times) to improve team velocity based on facts rather than opinions.
IT and Engineering Leads: Measure system health and flow metrics to identify technical debt while protecting team autonomy.
Operations, Legal, and Finance Teams: Track internal SLAs and monitor how long documents stay in "Review" to prevent administrative bottlenecks.
Marketing and Creative Teams: Ensure campaigns launch on schedule by pinpointing assets stuck in stages like "Design" or "Approval."
Atlassian Forge is a cloud app development platform built to help developers create secure, reliable, and scalable applications directly within the Atlassian ecosystem.
Atlassian is heavily investing in Forge as its next-generation cloud architecture and actively encouraging Marketplace vendors to transition. The primary driver behind this push is fundamentally enhanced application security and data control.
To standardize this level of security and reliability across the entire ecosystem, Atlassian is officially phasing out its legacy Connect platform. Starting September 17, 2025, the Atlassian Marketplace only accepts Forge apps for new submissions, and Atlassian will deliver all new extensibility features exclusively on the Forge platform. Here is what you need to know about your data.
When you initiate the update process, the system will ask for Jira admin approval for new permissions. Despite this prompt, nothing has changed regarding the application compliance posture or how it processes your Jira data.
The application accesses the exact same Jira data on your system required for reporting. It processes this data in the exact same region. Following the established privacy model, the application discards the data immediately after use.
Follow these exact steps to manually update Timepiece to the latest Forge version for your Jira environment:
Once approved, your Jira instance will be updated to the new version automatically. This process requires zero downtime and zero configuration changes to your existing reports. Please note that if your organization operates multiple Jira instances, you must repeat these exact steps for each individual instance.
We strongly recommend updating the application as soon as possible. Promptly completing this update ensures you unlock the latest capabilities and prevent any future disruption to your Agile metric tracking when the Connect version is officially deprecated.
If you require technical assistance with the update process or have specific compliance questions, please reach out directly to the OBSS Service Desk.
To learn more about Timepiece - Time in Status for Jira, visit its Atlassian Marketplace page.
Birkan Yildiz _OBSS_
0 comments