TRCKR-614 - trckr

← TRCKR-614

feature

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

Relationships Loading...

## Problem

The issue detail page displays the internal UUID (e.g., `a1b2c3d4-e5f6-7890-abcd-ef1234567890`), which is:
- Not useful to end users
- Visual clutter
- Takes up space
- Exposes internal implementation details

## Current Behavior

The issue detail view shows:
```
ID: a1b2c3d4-e5f6-7890-abcd-ef1234567890
Identifier: TRCKR-123
```

## Expected Behavior

Only show the human-readable identifier:
```
TRCKR-123
```

The UUID should:
- Not be displayed in the UI
- Still be used internally for API calls, data-attributes, etc.
- Optionally be available via browser dev tools or copy action if needed for debugging

## Scope

- Remove UUID display from issue detail modal
- Keep the human-readable identifier (e.g., TRCKR-123) prominently displayed
- Ensure UUID is still in data attributes for JavaScript/HTMX functionality
- Apply same principle to other entity detail views if they show UUIDs

## Acceptance Criteria

- UUID not visible in issue detail view
- Human-readable identifier clearly displayed
- No regression in functionality (editing, API calls still work)
- UUID still accessible in DOM for technical operations

Pull Requests (comma-separated URLs)

Attachments

Comments (2)

agent · 2025-12-26

## Implementation Complete **Changes made:** Removed UUID display from the `.detail-meta` section in 7 template files: - `server/templates/modals/issue_detail.html:299` - Removed `ID: {{ issue.id }} ·` - `server/templates/issue_detail.html:167` - Removed `ID: {{ issue.id }} ·` - `server/templates/modals/project_detail.html:253` - Removed `ID: {{ project.id }} ·` - `server/templates/project_detail.html:129` - Removed `ID: {{ project.id }} ·` - `server/templates/modals/milestone_detail.html:118` - Removed `ID: {{ milestone.id }} ·` - `server/templates/milestone_detail.html:83` - Removed `ID: {{ milestone.id }} ·` - `server/templates/modals/attachment_detail.html:84` - Removed `<div>ID: {{ attachment.id }}</div>` **Verification:** - All tests pass (870 passed, 1 pre-existing failure unrelated to this change) - Deployed to https://trckr.roboalch.com - Health check: `{"status":"healthy","version":"0.1.0","database":"connected"}` **Note:** UUIDs are still preserved in: - JavaScript variables (e.g., `const issueId = '{{ issue.id }}'`) - HTMX attributes (e.g., `hx-delete="/web/issues/{{ issue.id }}"`) - Data attributes for API functionality The human-readable identifier (e.g., TRCKR-123) is prominently displayed in the header of each detail view.

triage-agent · 2025-12-26

## Feature Triage Complete **Status:** NOT IMPLEMENTED - Ready to implement **Summary:** The feature request is valid. UUIDs are currently displayed in the `.detail-meta` section at the bottom of 7 detail page templates (issues, projects, milestones, attachments - both modal and standalone views). The human-readable identifier is already prominently displayed in the header. **Implementation Location:** - `server/templates/modals/issue_detail.html:299` - `server/templates/issue_detail.html:167` - `server/templates/modals/project_detail.html:253` - `server/templates/project_detail.html:129` - `server/templates/modals/milestone_detail.html:118` - `server/templates/milestone_detail.html:83` - `server/templates/modals/attachment_detail.html:84` **Complexity:** LOW - Simple template changes, remove 7 UUID display spans **Dependencies:** None **Implementation approach:** Remove the `ID: {{ entity.id }} ·` lines from each template. UUID is already preserved in JavaScript variables and data attributes for API functionality. See full triage report at /tmp/triage-TRCKR-610.md