TRCKR-514 - trckr

← TRCKR-514

feature

Created: 2025-12-26 • Updated: 2025-12-26

Relationships Loading...

## Problem

The 'created' field displays raw ISO datetime format:
```
2025-12-26T07:18:20.039870+00:00
```

This is not user-friendly and is in UTC rather than the user's local timezone.

## Expected Format

Display in a natural, human-readable format in the user's local timezone:
- `Dec 26, 2025 at 2:18 AM` (for US locale)
- Or relative: `2 hours ago` for recent times
- Hover/tooltip can show full datetime if needed

## Scope

Apply to all datetime displays across the web UI:
- Issue detail view (created, updated)
- Issue table (created column, updated column)
- Project detail/table
- Milestone detail/table
- Document detail/table
- Attachment detail/table
- Comments timestamps
- Any other datetime fields

## Implementation Options

### Option 1: Server-side (Jinja filter)
Create a Jinja filter that formats datetime:
```python
@app.template_filter('humanize_datetime')
def humanize_datetime(value):
    # Format to readable string
```

### Option 2: Client-side (JavaScript)
Use JavaScript to format `<time>` elements with `datetime` attribute:
```html
<time datetime="2025-12-26T07:18:20+00:00" class="local-time"></time>
```
JS converts to local timezone on page load.

## Acceptance Criteria

- All datetime fields display in human-readable format
- Times shown in user's local timezone (detected via browser)
- Consistent format across all entity views
- Optional: hover shows full ISO datetime for precision

Pull Requests (comma-separated URLs)

Attachments

Comments (2)

agent · 2025-12-26

Implementation complete. Created server/static/js/datetime-utils.js with formatDateTime() and getRelativeTime() functions. Updated all 17 template files to use data-datetime attributes. Fixed broken formatTimestamps() function in issue detail modal. All 870 tests pass.

triage-agent · 2025-12-26

## Feature Triage Complete **Status:** PARTIALLY IMPLEMENTED **Summary:** There is already a `formatTimestamps()` function in the issue detail modal, but it has a bug (`Invalid option` error with `toLocaleString`). The agents table has a working `updateRelativeTimes()` implementation that can be used as a pattern. Most templates just slice the ISO string (`[:10]` or `[:19]`). **Implementation Location:** - Create: `server/static/js/datetime-utils.js` (shared utility) - Modify: `base.html` to include the script - Modify: ~15 template files to use `data-datetime` attributes **Existing Bug to Fix:** `server/templates/modals/issue_detail.html` lines 598-618 - the `toLocaleString()` options are incompatible **Complexity:** Low-Medium See triage report: `/tmp/triage-TRCKR-425.md`