Connect end of support: what to do about your Jira worklog report

If your worklog report or timesheet app is built on Atlassian Connect, people on your site have started to see a notice inside it: “This app might stop working soon”. Your Jira admins see a warning beside it in Atlassian Administration too. This page says what changes on 31 January 2027 and what does not, how to check your own app, what to look for if it is the report your invoices or payroll come from, and how to move without losing a month. It ends with Logline, the worklog report we built on Forge.

The dates

• 17 September 2025: no new Connect apps on the Marketplace (Atlassian, 17 March 2025).
• March 2026: Connect descriptors frozen, so a Connect app can no longer change its Connect parts (the same announcement).
• 20 May 2026: the “This app might stop working soon” notice starts appearing inside Connect apps’ own screens (Atlassian developer community). From September 2026 it reaches every user of an app that uses any Connect feature, including apps that moved to Forge but kept some Connect parts.
• Late July 2026: a yellow warning on the Connected apps page of Atlassian Administration, for apps that only use Connect and for vendors who said they will not move or have not decided; a blue note, from September, for vendors who said they will (what admins see).
• 31 January 2027: end of support. It was December 2026 until Atlassian moved it on 3 August 2026 (Atlassian developer community).

What “might stop working” means

The notice is not a switch-off date. After 31 January 2027 Connect apps keep running, but in Atlassian’s words “only critical security vulnerabilities will be addressed and Connect feature deprecations will happen with little notice”, and breakages will become more frequent (Atlassian, 3 August 2026). The same post says over 95% of paid app seats have already moved to Forge.

So the risk for a worklog report is not that it disappears on 1 February. It is that the report someone runs at every month-end stops loading one day, and no fix is coming.

The admin warning reads: “This app is running on a platform that will be unsupported after January 2027. For migration plans or other available options, contact the vendor directly through the app’s Marketplace listing.” Atlassian publishes no list of replacement apps, and tells customers that no action is required beyond that (Atlassian, 6 August 2025).

Check your own app first

1. In Atlassian Administration, open Connected apps for your site and read the note beside each app: a yellow warning, a blue note, or nothing.
2. For each app with a warning, open its Marketplace listing and ask the vendor, through the listing’s support link, whether a Forge version is coming, and when. A blue note means the vendor has said it will move.
3. Write down what people use in it before anything changes: each saved report’s period, rows, columns and people, who it is shared with, and what gets exported and where it goes.

If the vendor has a Forge version on the way and a date before 31 January 2027, waiting for it is a fine answer. The rest of this page is for the reports with no such date.

What to look for in a replacement worklog report

• Built on Forge. The listing says so. A Runs on Atlassian badge also means the app sends no data outside Atlassian (Atlassian), which a security review will ask about.
• It reads Jira’s own worklogs, so people keep logging time as they do today and there is nothing to migrate: the hours are already in Jira.
• Read-only, if reporting is all you need. The listing’s Privacy and Security tab lists what an app may read and write.
• The views your teams use: a timesheet grouped by a field, a split by day, week or month, rolling periods, the worklogs with their comments, saved and shared reports, and an Excel export.
• Totals that match Jira’s. Compare a closed month in both apps. When two reports differ, it is nearly always the time zone that decides a worklog’s day, or worklogs that only some people may see (Making the totals match Jira’s time spent).

If all you need is one person’s hours for a month, Jira’s own search may be enough; Jira worklog report by user and month says how far it goes.

Moving, step by step

1. Install the replacement beside the old app. Both read the same worklogs, so neither changes what the other shows.
2. Rebuild each saved report once, from the list you wrote down, and share it with the same people or groups.
3. Compare last month in both, per person and per issue, before anyone relies on the new one.
4. Tell people where their reports are now. Put the weekly one on a dashboard if that is where they look.
5. Uninstall the old app once nobody opens it. Do it before 31 January 2027, while the old report still works if you need to check a figure.

With Logline

Logline is our app. It is a worklog report and timesheet built on Forge, for exactly this move:

• It reads Jira’s own worklogs, as the person viewing, with read-only permissions, so nobody sees a worklog Jira hides from them. Nothing leaves your Atlassian site, and it never changes a worklog or an issue.
• Apps › Logline opens on install with the last 30 days, every space you can see, by person then issue, split by week: the hours are there before you set anything up.
• Every view of a Connect worklog report has a place in it: a field grouping becomes Rows, the split becomes Columns, worklogs with their comments are the Worklogs view, the work ratio is an extra column, and saved reports are saved and shared the same way. Coming from a Connect worklog report lists each one.
• There is no importer: you rebuild each saved report once, and both apps can run side by side while you compare totals.
• It adds what a report on its own lacked: billable hours with their amount, hours against expected hours, gaps on working days with no time logged, and a weekly team timesheet on a dashboard.

What it does not do: timers, approvals or logging time. If your Connect app did those, look for a time-tracking app instead. More on the Logline home page.