Connect end of support and Jira time tracking apps
Atlassian is ending support for Connect, the older way of building Jira Cloud apps. This page sets out the dates, what Atlassian says end of support means, which Jira time tracking apps the Atlassian Marketplace currently lists as Connect apps, and how to check an app yourself. I make Saguaro Hours, a time tracking app built on Forge, so read the last section with that in mind.
The dates
From Atlassian's announcement, "Announcing Connect End of Support: Timeline and Next Steps" (published 2025-03-17, https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps ):
- September 17, 2025: new Marketplace apps must be built on Forge.
- March 2026: "Marketplace apps with a Connect descriptor can no longer be updated." Apps that have adopted the Forge manifest can still receive updates.
- End of support, first planned for Q4 2026. On 2026-08-03 Atlassian moved it: "We're extending the Connect end of support date from December 2026 to January 31, 2027" (https://community.developer.atlassian.com/t/connect-end-of-support-extended-to-january-31-2027/102002 ).
An app with a Forge manifest that still contains Connect modules is "considered a Connect app until all Connect modules are removed", according to the same announcement.
What end of support means for an installed app
Atlassian's announcement describes it as "use at your own risk": Connect gets no new features and only critical or security bugs are fixed. Customers keep access to Connect apps they have installed, but Atlassian calls that an undesired state because of the lack of support. All quotes and dates here were read on 2026-11-04.
So nothing is switched off on January 31, 2027 by that announcement alone. What changes is the support behind the app, and the vendor's ability to ship a fixed version on Connect, unless the app has adopted the Forge manifest.
Jira time tracking apps the Marketplace lists as Connect
The Marketplace API reports, for each app, whether its latest Jira Cloud version is a Connect app and when that version was released. These apps came back as Connect on 2026-11-04 (install counts change daily, so they are rounded):
| App | Vendor | Installs (about) | Latest Cloud version | Released |
|---|---|---|---|---|
| Clockify: Time Tracking & Timesheet | CAKE.com | 8,600 | 1.0.13-AC | 2023-05-18 |
| Harvest Time Tracking (Official) | Harvest | 2,400 | 1.5.5-AC | 2021-06-29 |
| Clockify: Time Tracking & Timesheet 2-Way Sync | CAKE.com | 1,200 | 1.0.2-AC | 2026-08-03 |
| Pivot Report: Roll Up Epic Issues, Worklogs & Time in Status | Colined | 900 | 1.2.105-AC | 2026-02-17 |
| TMetric: Time Tracker for Jira & Timesheet Reports | Devart | 700 | 2.1.8-AC | 2022-05-02 |
| Worklogs Report | Colined | 400 | 1.2.24-AC | 2025-04-26 |
This is what the Marketplace listed on that day, nothing more. A vendor may already be working on a Forge version, or may publish one under a new listing. Ask the vendor before deciding anything.
The other large time tracking apps came back as Forge on the same day, among them Timesheets by Tempo, Time Tracker for Jira Cloud (Tempo), Timesheet Tracking for Jira (Cappsule), Clockwork Lite and Pro, Worklogs by SolDevelo, Activity Timeline, Timetracker by STAGIL and Everhour.
How to check any app yourself
Open this address in a browser, with the app's key in place of KEY:
<https://marketplace.atlassian.com/rest/2/addons/KEY/versions/latest?hosting=cloud>
In the answer, "deployment" has "connect": true for a Connect app and "connect": false otherwise, and "release" has the date. To find an app's key, search by name at <https://marketplace.atlassian.com/rest/2/addons?hosting=cloud&text=NAME> and read the "key" field. For example, Clockify's key is clockify-timesheets-time-tracking-reports.
If you decide to move
- Look at where your time actually lives. If the app writes Jira worklogs, those stay in Jira when the app is removed, and any other time tracking app that reads Jira worklogs sees them. Time kept only in the vendor's own service stays there; export it from that service first.
- Export before you uninstall.
- Check the replacement's platform with the address above, so you only move once.
Saguaro Hours
Saguaro Hours for Jira is built on Forge and writes normal Jira worklogs as the signed-in user. Each person can import their own time from a CSV export of another tool (for example an export of Clockify, Harvest, TMetric, Toggl or Clockwork, or a spreadsheet) or from a calendar file; Jira does not let an app log work in someone else's name, so each person imports their own. Details: Import your own time. Moving from Tempo works differently, with an admin import: move from Tempo guide.
Status: Saguaro Hours was submitted to the Atlassian Marketplace on 2026-11-03 and is waiting for approval. The CSV and calendar import is built and tested on my development site as of 2026-11-04; it is newer than the build under review.
Related
- Jira time tracking apps compared
- How to get a worklog report in Jira Cloud
- Weekly timesheets in Jira
Email me when it's live
Saguaro Hours is free for up to 10 users. Email me when it's live and I will send one email on the day the listing is approved.
Clockify belongs to CAKE.com, Harvest to Harvest, TMetric to Devart, and Pivot Report and Worklogs Report to Colined. Saguaro Hours and LeDuc Systems LLC are not affiliated with any of them.