Foo Developer created FINERACT-3033:
---------------------------------------
Summary: Notifications: "Created At" time is 2 hours behind (UTC
returned without timezone instead of local time)
Key: FINERACT-3033
URL: https://issues.apache.org/jira/browse/FINERACT-3033
Project: Apache Fineract
Issue Type: Bug
Components: Organization
Reporter: Foo Developer
Assignee: Foo Developer
On the Notifications screen, the "Created At" time of every notification is 2
hours earlier than the real time of the action. The time shown is UTC, while
the rest of the portal (Audit Trails, Access Audit) shows local time
(Asia/Beirut, UTC+2). The API returns createdAt as UTC with no timezone offset,
so the screen cannot tell it is UTC and displays it as is.
Steps to reproduce
Create a client (or any action that raises a notification, e.g. create/approve
a savings account or make a deposit). Example on UAT: client 838 created by
mifos on 26 Oct 2026.
Open Notifications (bell icon > View all, or #/notifications).
Compare the "Created At" time with the time of the action, e.g. in Admin >
System > Audit Trails filtered on Entity = CLIENT.
Actual result
Notifications shows "New client created" at 2026-10-26T10:06:19.900905 (client
838, notification id 7641).
Audit Trails shows the same action (trail 20980, create Client 838 by mifos) at
2026-10-26 12:06:18, which is the correct local time.
GET /fineract-provider/api/v1/notifications returns "createdAt":
"2026-10-26T10:06:19.900905", in UTC with no "Z" or offset.
The same 2-hour gap shows on all notifications (e.g. "Savings account approved"
and "New savings account created" for savings account 1579 at 10:06:20 instead
of 12:06:20).
Expected result
Created At shows the local time of the action (12:06:19 for the example above),
consistent with Audit Trails and the rest of the portal. The API should either
return the time in the tenant timezone or include the timezone offset so the
frontend can convert it.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
