TRCKR-299 - trckr

← TRCKR-299

bug web ui

Created: 2025-12-12 • Updated: 2025-12-16

Relationships Loading...

The issue edit modal is missing the ability to edit the assignee field. Users should be able to assign or change the assignee when editing an issue.

## Current Behavior
The issue edit modal does not include an assignee field, so users cannot assign or reassign issues through the web UI.

## Desired Behavior
Add an assignee input field to the issue edit modal that allows:
- Viewing the current assignee (if any)
- Setting a new assignee
- Clearing the assignee

## Implementation

1. **Template changes** (`server/templates/partials/issue_edit_modal.html` or similar):
   - Add an assignee input field to the form
   - Position it logically with other issue metadata (near status/priority)
   - Pre-populate with current assignee value

2. **Form handling**:
   - Ensure the assignee field is included in form submission
   - Backend route should already support assignee updates via the API

3. **Input type options**:
   - Simple text input (free-form assignee names)
   - Or dropdown/datalist if there's a list of known assignees

## Acceptance Criteria
- [ ] Assignee field is visible in the issue edit modal
- [ ] Current assignee is shown when editing existing issues
- [ ] Assignee can be changed and saved
- [ ] Assignee can be cleared (set to empty/null)
- [ ] Changes persist after saving

Pull Requests (comma-separated URLs)

Attachments

Comments (1)

agent · 2025-12-12

**Investigation Complete** After thorough investigation, I confirmed that the assignee field is **already fully implemented** in the issue edit modal. **Evidence:** 1. **Template code** (server/templates/modals/issue_detail.html, lines 41-44): - Assignee input field exists with proper value binding and change detection - Uses `data-original` attribute for tracking changes - Integrated with `checkForChanges()` and `saveIssueChanges()` JavaScript 2. **Backend support** (server/routes/web.py): - Line 505: PATCH route accepts `assignee` parameter - Lines 528-529: Updates assignee in database 3. **Visual verification**: - Deployed to production server (trckr.roboalch.com) - Opened issue TRCKR-299 in web UI via chrome-devtools - Screenshot confirms assignee field is visible in top row between Priority and Milestone - Field shows current value 'agent' and is editable 4. **Git history**: - Assignee field was added in commit 8141325 (TRCKR-319) on 2025-12-08 - This issue was created on 2025-12-12, 4 days after the feature was implemented 5. **Test results**: - All 1229 tests PASS - No failures or errors **Conclusion:** The assignee field functionality requested in this issue already exists and is working correctly. The issue description appears to be outdated.