Timepiece – Time in Status for Jira has been migrated from Atlassian Connect to Atlassian Forge. This page explains what’s changing, why you’re seeing new permission requests, and how to update the app in your Jira instances manually.
Summary
Forge is Atlassian’s next-generation cloud platform. Atlassian is making heavy investments in Forge as its next-generation cloud development platform, and is encouraging marketplace vendors to migrate their apps to this new infrastructure.
We successfully migrated Timepiece - Time in Status for Jira to the Atlassian Forge platform, and it is now working as a Forge app with a Remote Backend.
The Connect version will remain online for a limited time to keep the customer environments operational until each instance is updated.
New features and fixes will be delivered to the latest Forge version only, and the Connect version will be shut down after the migration period. (Timeline not set yet)
We strongly recommend updating the app as soon as possible to prevent any disruption to your reporting workflows and to unlock our latest capabilities.
When upgrading the app, you will notice that the update requires Jira admin approval for new permissions. Rest assured that nothing has changed regarding the app’s compliance posture and how it processes and stores your Jira data.
The app accesses the exact same Jira data on your system, processes it in the same region (AWS us-west-2), and discards it immediately after use, just as it did before. The scope of the data it handles and the location where it processes it remain identical.
The only change, and the only reason for the new permission request, is that the app now collects product analytics and error data. This includes anonymized error messages and high-level usage metrics (for example, which screens are viewed or which buttons are clicked). This analytics and error data does not contain any personal data or Jira data.
Feel free to check our Privacy Policy for more details.
Timepiece - Time in Status for Jira Cloud has always been a SaaS product. All app updates were delivered seamlessly to all Jira instances and will continue to be so in the future. However, this Forge migration introduces new product analytics permissions in the app manifest. Because of this, Jira requires an administrator to manually approve the update once.
Future features, improvements, and bug fixes will be delivered only to the Forge version. Remaining on the old Connect version increases the risk of compatibility issues and missing critical fixes.
Follow these steps to manually update Timepiece to the latest version for your Jira:
Once approved, your Jira instance will be updated to the new version without downtime or configuration changes. Please note that, if you have multiple Jira instances, you’ll need to repeat the steps for each instance.
If you need assistance with the update or have questions, please reach out to the OBSS Service Desk.
To learn more about Timepiece - Time in Status for Jira, visit its Atlassian Marketplace page.