Skip to content
Menu
HelpConnect time report alternatives for Jira Cloud

Connect time report alternatives for Jira Cloud

Checked on 13 November 2026 against the Marketplace listings, their pricing and Atlassian’s documentation.

Logline is our app. It is the last option here, after Jira’s own search and the vendor. Each other app’s strength is stated from its own listing, read on 13 November 2026. The listings change, so check them again before you choose.

Three Connect apps build time reports for Jira Cloud, and Atlassian ends support for Connect on 31 January 2027. Jira admins see a warning beside Connect apps on the Connected apps page; Connect end of support for Jira worklog reports has the dates and what the warning means. This page covers the three, and the options for a team that reports on its time from one of them.

Which option fits

  • Stay, if the vendor is moving: ask the vendor (option 1).
  • Hours per person for a month, now and then: Jira’s own search (option 2).
  • Work logs from several Jira sites in one report: Time Reports for Jira (option 3).
  • Time per work item in each sprint, and a report by email after it closes: Simple Time Tracker Report (option 4).
  • Timers, suggestions and a summary of your own hours: Time Assistant (option 5).
  • The same reports on Forge, changing nothing in Jira, for one site: Logline (option 6).

1. Ask the vendor

Atlassian’s advice for any Connect app is to contact the vendor through the app’s Marketplace listing. A blue note beside the app on Connected apps means the vendor has said it will move; a yellow warning means it has not said so.

2. Jira’s own search (free)

JQL finds the work items with time logged in a period (worklogDate, worklogAuthor), but the Time Spent beside each one is its all-time total, and Jira has no report of hours per person per period (JRACLOUD-97253). For an occasional figure that can be enough. Jira worklog report by user and month walks through it.

3. Time Reports for Jira

Built by Rozdoum. Its listing says it “generates work log reports, aggregated from multiple Jira instances”. It pulls the work logs of several Jira sites into one report, with two views: a “User by Day” grid of work logs by user and source, and an “Issues by Source” report sorted by work item. Its latest Cloud version is a Connect release, 1.0.4-AC, dated 21 October 2021 (Marketplace REST API, read 13 November 2026). Its listing says the partner has filled in the Privacy and security questionnaire.

What it does that Logline does not: one report across several Jira sites. Logline reads the Jira site it is installed on.

4. Simple Time Tracker Report for Jira

Built by simplereport.technology. Its listing says it helps you “understand which issues your team spends time on during a sprint and how much each issue or issue type costs you”, and that it sends a report to an email address after a sprint closes. It also compares spent time by sprint with earlier sprints, and shows a table of work items with the time each person logged. Its latest Cloud version is a Connect release, 1.0.1894-AC, dated 5 June 2021 (Marketplace REST API, read 13 November 2026). Its listing says the partner has not filled in the Privacy and security questionnaire, so ask for it before a security review.

What it does that Logline does not: a report by email after each sprint. Logline sends no email.

5. Time Assistant

Built by SolDevelo. Its listing says it offers “time and workload tracking”: a view of the work items you worked on across chosen periods, suggestions of work items that may need time logged, a favourites gadget, active timers, and a summary of your logged hours over a period. It is part of Atlassian’s Marketplace Bug Bounty programme, and the partner has filled in the Privacy and security questionnaire. Its latest Cloud version is a Connect release, 1.1.5-AC, dated 28 April 2025 (Marketplace REST API, read 13 November 2026). Atlassian bills it: 10 people free, and the Pricing tab of its listing gives the cost above that (read 13 November 2026).

Only the hours summary is a report, and that part is the one this guide compares. Logging time, timers and suggestions are not reporting, and Logline does none of them.

The same vendor publishes a worklog report, Worklogs – Time Tracking, Time Reports, Timesheets. Its listing carries the Runs on Atlassian badge (read 13 November 2026).

6. Logline (ours)

Logline is a worklog report and timesheet built on Atlassian Forge. Inside Jira, no servers: no data leaves your Atlassian site, and it changes nothing in Jira. It reads the work logs as the person viewing, so nobody sees a work log Jira hides from them.

  • A timesheet grouped by a field, up to two levels, under Rows.
  • A daily, weekly or monthly split under Per.
  • Fixed and rolling periods.
  • Work logs as rows, with their comments, in the Worklogs view.
  • Saved reports, public or restricted, shared with people or groups.
  • Excel and CSV.

What it does not do: send email, run timers, log time, or read more than the one Jira site it is installed on. Free for up to 10 people; above that, Atlassian bills it per person, and the Pricing tab of its listing gives the cost for your site. Coming from a Connect worklog report lists where each view of a Connect report has its place in Logline.

Moving

  1. Install the replacement beside the old app. Both read the same work logs, 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.
  3. Compare a closed month in both, per person and per work item, before anyone relies on the new one.
  4. Uninstall the old app once nobody opens it, before 31 January 2027, while the old report still works if you need to check a figure.

There is no importer. More on the Logline home page.

Simple Time Tracker Report for Jira, Time Reports for Jira, Time Assistant and Worklogs – Time Tracking, Time Reports, Timesheets are trademarks of their owners; this page is not affiliated with or endorsed by them.

A Logline report on 1 to 30 September, from its scope row down: Scope set to Spaces with ACME, INT and NWND chosen, Whose time Everyone, Period 1 Sep – 30 Sep with its arrows, Show report, then Save, Reports, Copy link and Download on the same line; under it one grey line, “1 Sep – 30 Sep · 447 worklogs · Counted in America/New_York”, with How this is counted and Recalculate. Then the Timesheet tab and its chips: Rows Epic, Then by Work item, Per Total only, Billable only, Sort Remaining %, Descending and Columns. Rows are epics, then work items, with Total, Billable, Amount and the estimate columns, the Total row first: 652h 45m, 404h 30m of it billable at 62%, USD 56,655. ACME-1 Q4 storefront, “2 over”, has 223h 45m, 195h of it billable, its work items furthest over first: ACME-2 Checkout redesign, 14h logged against 12h estimated, a yellow 117%, and a red 133% where it ends. ACME-7 Order history page, 19h, is opened to its nine worklogs, each with its date, Mitch Davis or Alana Grant, the hours and the comment, such as “Tue 1 Sep 14:00 · Mitch Davis · 2h · Order list layout”. NWND-1 Mobile app v2 has 162h 30m, 134h of it billable.
September in Logline by epic, then work item, with billable hours and their amount: a Connect time report’s timesheet, on Forge.

Try it on your own worklogs

Free for up to 10 users, then billed per user by Atlassian.