Worklogs Report alternatives for Jira Cloud
Checked on 13 October 2026 against the Marketplace listings, Worklogs Report’s documentation and demo, and Atlassian’s documentation.
Logline is our app. It is option 4 here: asking the vendor and Jira’s own search come first, and what Worklogs Report does that Logline does not is at the end. Facts checked 13 October 2026.
Worklogs Report, by Colined, is a worklog report and timesheet for Jira Cloud built on Atlassian Connect. Its latest Cloud version, 1.2.24, was released on 26 April 2025 (its Marketplace listing). Atlassian ends support for Connect on 31 January 2027, and 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. If your team’s timesheets come from Worklogs Report, here are the options, cheapest first.
Which option fits
- Stay, if it is moving: ask the vendor (option 1).
- One person’s hours for a month, now and then: Jira’s own search (free, option 2).
- Timers, approvals or locked periods as well: a time-tracking suite (option 3).
- The same reports, built on Forge, changing nothing in Jira: Logline (option 4).
- Your people log time in Tempo Timesheets: not Logline (see the last section).
1. Ask the vendor
Atlassian’s advice for any Connect app is to contact the vendor through the app’s Marketplace listing. If Colined announces a Forge version with a date before 31 January 2027, staying may be the least work. Two places to look:
- The note beside the app on Connected apps in Atlassian Administration: a yellow warning means the vendor has said it will not move, or has not said; a blue note means it has said it will.
- The listing’s version history, for a release built on Forge.
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, not the period’s, and Jira has no report of hours per person per
period
(JRACLOUD-97253).
For an occasional figure that can be enough; for a monthly timesheet it
means a spreadsheet every month. Jira worklog report by user and
month walks through it.
3. A time-tracking suite
If you also want timers, approvals or locked timesheet periods, a time-tracking app does reports too, usually at a higher price per user. It is a bigger change: people log time in a new way.
4. Logline (ours)
Logline is a worklog report and timesheet. Inside Jira, no servers: your data never leaves your site. Built on Atlassian Forge. It changes nothing in Jira and reads Jira’s own worklogs as the person viewing, so nobody sees a worklog Jira hides from them. Each view of a Connect worklog report has a place in it (Coming from a Connect worklog report lists them):
- Timesheet grouped by a field: Rows, up to two levels, by parent, resolution, reporter, creator and custom fields as well as person, epic, status and the rest.
- Daily, weekly or monthly split: Per.
- Fixed and rolling date ranges, and « »: Period, then the ‹ and › arrows.
- A day’s worklogs on hover: any figure in the timesheet opens the worklogs it adds up, with their comments.
- Worklogs as rows, with comments: the Worklogs view.
- Up to three work item fields beside the worklogs: as many as you need, under Columns.
- Time units in days: Hours format, Decimal days.
- Work ratio: Columns, Logged (all time).
- Grouping by Jira group: Whose time, Jira groups, then Rows, Jira group.
- Jira’s own filters as the source: Scope, Saved filter: Jira’s own filters are listed first.
- Saved reports, public or restricted, with report admins: Save, then Share, with Editors.
- Favourites and recently visited: Saved reports, Favourites and Recently opened, with a search.
- A Jira admin changing a report’s owner: Logline settings, Saved reports.
- Full-access users, the others seeing their own worklogs: Logline settings, Who sees whose worklogs.
- The Jira time zone for everyone: Logline settings, One time zone for everyone.
- Excel with a Summary and a Breakdown sheet: Download, then Excel, a Summary and a Worklogs sheet, work item keys as links; or CSV.
There is no importer: rebuild each saved report once, and run both apps side by side while you compare the totals of a closed month.
What Logline does that Worklogs Report does not
From its Cloud documentation and its public demo, read on 13 October 2026:
- Any field first. Its rows are always people, then one field. Logline’s first level can be an epic, a space, a client field or a sprint, with people under it.
- More to group by. Components, labels, fix versions, sprints, assignees and multi-value fields, which it cannot group by.
- JQL as the source, besides spaces and saved filters.
- Billable hours and their amount, by a label, a field or JQL, with hourly rates per space or person.
- Hours against expected hours, and gaps on working days with no time logged.
- Periods. Today, Yesterday, Last 7 days, Last 90 days, this and last quarter, this and last year, and Last 2 weeks in one Period list, and the week starting on the day your team’s does; its weeks start on Monday.
- On the work item and the dashboard. A work item panel with time against the estimate, its line in the work item’s Details, and a dashboard gadget of a saved report. It has neither.
- CSV beside Excel.
- Sort by in the Worklogs view.
Two differences a security review will ask about:
- Permissions. Logline asks to read Jira and keep its own settings, nothing more. The Marketplace’s record of Worklogs Report’s current version lists Connect’s Read, Write and Delete permissions and both of its administration permissions, up to Full Administration.
- Where the app runs. Logline runs on Atlassian’s Forge platform with no server of its own. A Connect app runs on its vendor’s servers.
One difference shows on screen: Jira draws Logline’s pages with its own components, so they look like the rest of Jira. A Connect app’s pages are a frame its vendor fills, in its own design.
Logline is free for sites with up to 10 Jira users; Worklogs Report is paid from the first user, a flat price up to 10. Above that, both are billed per user by Atlassian, and the Pricing tab of each listing gives the exact cost for your site.
What Worklogs Report does that Logline does not
- Tempo Timesheets. Its listing says it “works both with default Jira time tracking and Tempo Timesheets”. Logline reads only Jira’s own worklogs, and time logged in Tempo reaches Jira under Tempo’s app account, so Logline shows those hours under Tempo, not the person (the question on our questions page). If your people log time in Tempo, Logline is not the replacement.
- Logging time. Its report has a Log Work button, and edits a worklog from the report. Logline only reads: people log time in Jira as they do today, and Logline asks for no permission to change it.
- A board of worklog cards. Its Cards view lays a week’s worklogs out as cards by day. Logline shows the same worklogs in the Worklogs view and behind each day’s figure.
- A track record. Worklogs Report has 404 installs and 18 reviews averaging 4.4 stars, is in Atlassian’s Cloud Fortified programme and takes part in its bug bounty. Logline is new: it has none of these yet.
- A demo with the vendor. Its listing offers a one-to-one demo.
What Logline does not do at all: timers, approvals or logging time. More on the Logline home page.
If your site also runs Colined’s other Connect app, which rolls up estimates and draws pivot report, Sumline’s guide covers it the same way.
Worklogs Report and Colined, Tempo and Tempo Timesheets are trademarks of their owners; this page is not affiliated with or endorsed by them.
