Project Issues button navigates to missing route (SZ-66)

rk@tigase.net opened 3 weeks ago

Summary

On the project list view, clicking the "Issues" button for a project navigates to a route that is not registered in the application router, resulting in an empty page.

The intended workflow is correct, but the corresponding route is missing in App.tsx.

Problem

When clicking the "Issues" button for a project, the application navigates to:

/app/projects/{projectId}/issues

However, this route is not defined in App.tsx, resulting in the following error:

No routes matched location "/app/projects/18/issues"

As a result:

The Issues button appears to work but leads to an empty page
Users cannot navigate to a project’s issues via the project list
The workflow feels broken despite the underlying functionality existing

Expected Behavior

Clicking the "Issues" button for a project opens the project’s issues page
The route /app/projects/{id}/issues is properly registered and mapped to the issues list component
The issues list displays issues scoped to the selected project

Root Cause

Missing route definition for /app/projects/:projectId/issues in App.tsx

Proposed Fix

Add the missing route in App.tsx
Map the route to the existing project issues list component
Ensure the projectId route parameter is correctly passed to the component

Acceptance Criteria

Navigating to /app/projects/{id}/issues renders the project’s issues list
Clicking the "Issues" button from the project list opens the correct page
No routing errors are logged in the console

Time Estimate

Add missing route in App.tsx: 10–15 minutes
Verify navigation and basic regression testing: 10–15 minutes

Total estimated effort: 20–30 minutes

Activities

rk@tigase.net commented 3 weeks ago

rksuma@Ramakrishnans-MacBook-Pro sztab % git checkout -b bugfix/1.7.1
Switched to a new branch 'bugfix/1.7.1'
rksuma@Ramakrishnans-MacBook-Pro sztab %

rk@tigase.net changed state to 'In Progress' 3 weeks ago
Previous Value Current Value
Open

In Progress
rk@tigase.net commented 3 weeks ago
Fixes:

Fix 1: Add the missing route in App.tsx:

<Route path="projects/:projectId/issues" element={<IssuesPage />} />

Fix 2: Make IssuesPage project-aware - Right now, IssuesPage always loads global issues
rk@tigase.net commented 3 weeks ago

Artur,

The “Issues” button was navigating to the correct URL (/projects/:id/issues), but the route was missing, which is why it rendered an empty page. That’s now fixed. In this project-scoped view, the project context is fixed and the project-related search filters are disabled, with filters and quick-filters operating only within the selected project. To explore issues across projects or change project scope, the Issues entry in the sidebar opens the global view.

Do you agree with this approach?

This will go out in the 1.7.1 bug-fix release.
rk@tigase.net changed fields 3 weeks ago
Name Previous Value Current Value
Version
empty
1.8
Artur Hefczyc commented 3 weeks ago

+1
rk@tigase.net commented 3 weeks ago

fixed in 1.8
rk@tigase.net changed state to 'Closed' 3 weeks ago
Previous Value Current Value
In Progress

Closed
Login to comment

Previous Value	Current Value
Open	In Progress

Name	Previous Value	Current Value
Version	empty	1.8

Previous Value	Current Value
In Progress	Closed

Type	Bug
Priority	Normal
Assignee	rk@tigase.net
Version	1.8
Sprints	n/a
Customer	n/a

Issue Votes (0)

Watchers (3)

Reference

SZ-66