Short Summary of the Bug
Packet Status timeline hardcodes IST (+0530) timezone; timestamps not shown in local/deployment timezone
Description
Description:
On the Packet Status page, the timeline formats createdDateTimes using Angular's DatePipe with a hardcoded +0530 (IST) timezone offset. As a result, all timeline timestamps are always converted to and displayed in IST, regardless of the deployment country or the viewer's local timezone. The backend (admin-services) returns createdDateTimes in UTC with no timezone logic, so this is purely a UI defect.
Location:
- packet-status.component.html line 45 — {{item.createdDateTimes | date:'medium':'+0530'}}
- packet-status.component.html line 48 — {{item.createdDateTimes | date:'medium':'+0530'}}
Steps to reproduce:
- Log into Admin UI → Packet Status.
- Enter a valid Registration ID and search.
- Expand the Timeline (View More) and observe the timestamps against each stage (e.g. "Jul 29, 2026, 3:42:19 PM").
Actual result:
Timeline timestamps are always displayed in IST (+0530), because the timezone offset is hardcoded in the template — incorrect for any non-IST deployment or viewer.
Expected result:
Timeline timestamps should be displayed in the deployment/local (or configurable) timezone. Since the backend value is UTC, it should be rendered in the browser's local timezone (matching the existing Bulk Upload pattern new Date(ts + "z").toLocaleString()).
JIRA link: https://mosip.atlassian.net/browse/MOSIP-45373
Short Summary of the Bug
Packet Status timeline hardcodes IST (+0530) timezone; timestamps not shown in local/deployment timezone
Description
Description:
On the Packet Status page, the timeline formats createdDateTimes using Angular's DatePipe with a hardcoded +0530 (IST) timezone offset. As a result, all timeline timestamps are always converted to and displayed in IST, regardless of the deployment country or the viewer's local timezone. The backend (admin-services) returns createdDateTimes in UTC with no timezone logic, so this is purely a UI defect.
Location:
Steps to reproduce:
Actual result:
Timeline timestamps are always displayed in IST (+0530), because the timezone offset is hardcoded in the template — incorrect for any non-IST deployment or viewer.
Expected result:
Timeline timestamps should be displayed in the deployment/local (or configurable) timezone. Since the backend value is UTC, it should be rendered in the browser's local timezone (matching the existing Bulk Upload pattern new Date(ts + "z").toLocaleString()).
JIRA link: https://mosip.atlassian.net/browse/MOSIP-45373