Summary

Clicking anywhere on a project entry in the project list currently opens the "Edit Project" dialog. This is unexpected behavior. Clicking a project should navigate to the project's default view (for example, issues list or project dashboard), not open the edit form.

Problem

In the project list view, the entire project row is clickable and mapped to the "Edit Project" action.

This causes several usability issues:

• Users accidentally open the edit dialog when they intend to view the project
• Editing is treated as the default action instead of a secondary action
• There is no clear way to navigate into a project without triggering edit mode

This behavior is inconsistent with common UX expectations, where:

• Clicking a list item navigates to its detail view
• Editing is an explicit action (button, icon, or menu)

Expected Behavior

• Clicking on a project row should navigate to the project's default page
• The default page should initially be the project's issues list or a lightweight project dashboard
• Editing project metadata should be available via an explicit "Edit" button or action menu

Suggested UI Changes

• Make the project row click navigate to /projects/{id} (or equivalent)
• Move the "Edit Project" action to:
  • A dedicated edit button, or
  • A contextual menu (three-dot menu) on the project row
• Define a clear project landing page (issues list initially; dashboard can be added incrementally)

Acceptance Criteria

• Clicking a project row no longer opens the Edit Project dialog
• A project default page is displayed on row click
• Editing project details requires an explicit user action
• No regression in existing project editing functionality

Time Estimate

• Frontend routing and click behavior update: 1.5–2 hours
• UI adjustments (edit button or menu): 1 hour
• Basic verification and regression testing: 0.5–1 hour

Total estimated effort: 3–4 hours