TRCKR-349 - trckr

← TRCKR-349

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

Relationships Loading...

## Bug Description
When a project is selected via the sidebar, the project column should automatically be hidden from the issues datatable since it's redundant - all displayed issues belong to the selected project. This behavior appears to have regressed, possibly introduced when the column view filtering setting was added.

## Steps to Reproduce
1. View the issues page with no project filter (project column visible)
2. Select a project from the sidebar
3. Observe that the project column remains visible in the datatable

## Expected Behavior
When filtering by a specific project via the sidebar:
- The project column should automatically be hidden from the datatable
- This saves horizontal space and removes redundant information
- When the project filter is cleared, the project column should reappear

## Actual Behavior
The project column remains visible even when filtering by a single project.

## Possible Cause
This regression may have been introduced when implementing the column view filtering setting feature. The auto-hide logic may need to be reconciled with the user's column visibility preferences.

## Acceptance Criteria
- Project column auto-hides when a project is selected in the sidebar
- Project column reappears when project filter is cleared
- Behavior works correctly alongside the column visibility settings feature

Pull Requests (comma-separated URLs)

Attachments

Comments (2)

qa-agent · 2025-12-16

## QA PASSED See detailed QA report document: 743ea7f6-20c3-44ce-83ef-f5c71a26371a **Verification Summary:** All test cases passed successfully. The fix works correctly on production. **Tests Performed:** 1. ✓ No project filter → Project column visible 2. ✓ Single project filter (UUID) → Project column hidden 3. ✓ Single project filter (KEY) → Project column hidden 4. ✓ Sidebar navigation → Project column auto-hides 5. ✓ "All Projects" → Project column reappears **Code Review:** - Server-side template: Correctly applies hidden class based on project_filter length - Client-side JavaScript: Respects data attribute and preserves hidden state - Backend routing: Properly resolves both UUIDs and project keys **Regressions:** None detected. All existing functionality continues to work correctly. **Recommendation:** Issue verified working as intended. Marking as done.

agent · 2025-12-16

## Fix Applied **Problem Found:** The server-side Jinja2 template correctly added the `hidden` CSS class to the project column (header and cells) when a single project was selected in the sidebar. However, the JavaScript `loadColumnVisibility()` function that runs on page load was overriding this by restoring the user's saved column visibility preferences from localStorage, which would remove the `hidden` class. **Changes Made:** 1. **server/templates/partials/issues_table.html** (line 2): - Added `data-single-project-filter` attribute to the `issues-table` div - This communicates the project filter state from server-side template to JavaScript 2. **server/templates/issues.html** (lines 311-344): - Modified `loadColumnVisibility()` to check the new data attribute - When a single project is selected (`data-single-project-filter="true"`): - Skips restoring saved project column visibility - Sets the project column checkbox to unchecked and disabled - Lets the server-side `hidden` class remain in effect **Verification:** - Ran automated Playwright tests covering all acceptance criteria: - Test 1: No project filter - column visible: PASS - Test 2: With project filter - column hidden: PASS - Test 3: Filter cleared - column visible: PASS - Visual verification via screenshots confirms the fix works correctly - All existing server tests pass (84 tests) **Files Changed:** - `/server/templates/partials/issues_table.html` - `/server/templates/issues.html`