nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue with "Automated Log Work Report Gadget" becoming unresponsive on Jira Cloud Dashboard

Tolga Pekiş

Hello Support Team,

We are experiencing an issue where the "Automated Log Work Report Gadget" on our Jira Cloud Dashboard is unresponsive and failing to load/generate worklog reports.

Best regards,

Tolga

Accepted answers

Anwesha Pan

Thanks for providing more details @Tolga Pekiş 🙂

This is is entirely on the vendor's hosting infrastructure. Looks like the SSL/TLS certificate for the vendor's backend server expired on September 29, 2026, hence you are receiving the error.

Please raise a support ticket via their Atlassian Marketplace Support Portal

Hope they are able to resolve the issue quickly since this is certificate incident. 📢

Thanks,
Anwesha

All comments

Anwesha Pan

Hi @Tolga Pekiş 👋🏻

First of all, welcome to community! ✨

I am sure you would have already tried the below options:

Check if you are facing the issue in Incognito mode as well
Check if it's happening in both Edge and Chrome
Check if third-party cookies and cross-site tracking are not blocked for *.atlassian.net

You could also try the below troubleshooting steps:

Inspect the Developer Console:

Press F12 (or right-click → Inspect) and open the Console and Network tabs.
Reload the dashboard.
Look for:
- HTTP 504 / Gateway Timeout: Indicates Jira Cloud or the app backend timed out fetching worklog entries.
- HTTP 401 / 403 (Unauthorized / Forbidden): Indicates a missing permission or expired auth token.
- Uncaught JavaScript Errors: Highlights frontend rendering bugs or broken payload handling.

I hope this helps & resolves your issue. 🙂

Thanks,
Anwesha

Tolga Pekiş

Hi @Anwesha Pan ,

Thanks for the suggestions!

I checked all of your suggestions, but unfortunately none of them resolved the issue.

The issue persists in Incognito mode, in both Chrome and Edge, and on a completely different network (mobile hotspot), so it is not related to browser extensions, cookies or our corporate network.
I am attaching screenshots of the errors from the browser console. Based on these, I believe the issue is not on our side.

The browser blocks the gadget with net::ERR_CERT_DATE_INVALID. The SSL certificate of the app's server (alw-2.gebsun.com, issued by Amazon) expired on September 29, 2026 (screenshot of the certificate details attached).

Best regards,

Tolga

Anwesha Pan

Thanks @Tolga Pekiş for providing more details with the screenshots. 👍️

This is definitely not related to your browser or Jira dashboard. It looks like to be related to the certificate issue which expired on Sep 29, 2026.

Please feel free to raise support ticket for the Atlassian marketplace app.

Hope they are able to resolve the issue quickly! 🙂

Thanks,
Anwesha

Anwesha Pan

Thanks for providing more details @Tolga Pekiş 🙂

This is is entirely on the vendor's hosting infrastructure. Looks like the SSL/TLS certificate for the vendor's backend server expired on September 29, 2026, hence you are receiving the error.

Please raise a support ticket via their Atlassian Marketplace Support Portal

Hope they are able to resolve the issue quickly since this is certificate incident. 📢

Thanks,
Anwesha

Tolga Pekiş

Hi Anwesha,

Thank you for your help and support.

I have raised a support ticket and will share an update here once the issue is resolved.

Best regards,
Tolga

we are suffering from same issue, and portal website (jira potral) is not working as we never receive and password reset or and email confirmation.

Atlassian need contact vendor by phone to share the issue asap, this is a blocking company process.

Nick [CodeCove]

Since the vendor won't be fixing this, it's worth checking where your hours live: open an issue your team logged time on and look at the Work log tab. If the entries are there, any app that reads native Jira worklogs will show your history straight away. Timesheets for Jira does that, it's free, and it has a dashboard gadget, so the report can go back where it was. Full disclosure, I work on it. If something your team relied on in Automated Log Work is missing, tell me here and we'll look at adding it.

thank you, we do not know if it will be fixed, but after tried your plugin in export, a lot columns is missing : organization name, reporter name, worklog comment, assignee name …

then group by organization and list of issues per one month

then "save the report and give a name"

Nick

Alfred Samanga (Resilia Tech)

@eb the columns you listed are all native Jira fields, so most of that monthly report can be rebuilt without any gadget:

Monthly list, saved by name: save a filter such as worklogDate >= startOfMonth(-1) AND worklogDate < startOfMonth(), name it ("Worklogs – September 2026") and share it. In list view use Configure columns to add Organizations, Reporter, Assignee and Σ Time Spent, then Export → CSV (current fields). Sorting or a pivot by Organizations in Excel gives the per-organization grouping.
Worklog comments and per-entry dates: those aren't in the CSV export, but the REST API has them: GET /rest/api/3/search/jql?jql=<that filter>&fields=worklog,reporter,assignee,<your Organizations field id>. Each worklog carries author, started, timeSpentSeconds and comment; keep only entries whose started date is in the month (the embedded list is capped at 20 per item, so fetch /rest/api/3/issue/{key}/worklog for busy items). Power Query or a short script turns that into the monthly table, grouped by organization.
Dashboard: a Workload Pie Chart gadget on the same saved filter (statistic type Assignee, time field Time Spent) puts a per-person view back on the dashboard.

thank you à lot to take Time for this comment. But max you expect this from non-developer and 60y old person? That’s why we use plugin … it is very crazy that jira not offer such a logical worklog export in 2026, and it seems Automated Log Work plugin works again. And we will find another option to not depends on this.

Alfred Samanga (Resilia Tech)

Fair point, and well made. The API route is for teams with a developer handy; nobody should need one for a monthly export. Glad the gadget is back.

When you look at other options, two things worth checking so this doesn't happen again: that the app reads Jira's own worklogs (so your history is already there and nothing needs migrating), and that it runs entirely inside Atlassian, with no vendor server or certificate that can expire. Atlassian marks those apps "Runs on Atlassian" on the Marketplace listing.

Levente Szabo _Midori_

@eb

FWIW, I think a monthly worklog export with organization, reporter, assignee, and comments is a fair thing to expect without writing code, so here is a route that needs none.

Better Excel Exporter for Jira adds Excel export views to the work item search, so you can keep the saved filter and the columns you already have in the list view:

Pick the worklogs export view in its repeating mode. Every worklog gets its own row with author, date, time spent and the worklog comment, and your Organizations, Reporter and Assignee columns are repeated on each row.
Filter that sheet to the month you need by worklog date, and a pivot table on Organizations gives you the per-organization totals. There is also a ready-made Worklog Report with pivot tables and charts by user and project, if you’d rather start from that.
If you want the file in your inbox every month, the free Better Excel Automation app emails the same export from a scheduled Jira Automation rule.

(I'm part of Midori, the company behind Better Excel Exporter.)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira