stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Add a mobile My Work inbox backed by supported Gitea search #115

New Issue
Closed
opened 2026-08-06 15:19:22 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-06 15:19:22 +00:00
Member
Copy Link

Evidence

The dashboard currently fetches user/issues and user/pulls, which return 404 on this Gitea deployment. As a result, the central work view degrades to empty lists even though /repos/issues/search returns real cross-repository work. Mobile currently only collapses the desktop grid and puts context/AI panels before actionable items. Historical issues and recent commits contain no supported-search or mobile action-inbox implementation.

User flow

Open the dashboard on a phone, see a prioritized My Work queue immediately below the header, filter All/Issues/PRs, and tap a full card to open the correct forge item. Successful data remains visible if a later refresh fails.

Acceptance criteria

  • Use supported Gitea search APIs to return real assigned/open issues and pull requests without relying on /user/issues or /user/pulls.
  • Normalize repository identity, URL, labels, assignees, and updated time for cross-repository items.
  • Render My Work before auxiliary panels on narrow screens, with All/Issues/PRs filters and 44px tap targets.
  • Rank priority-labelled then assigned work deterministically and distinguish duplicate item numbers by repository.
  • Preserve the last successful queue on refresh failure and mark it stale.
  • Add behavioral tests, including endpoint selection, deterministic ranking/rendering, and mobile layout semantics.
## Evidence The dashboard currently fetches `user/issues` and `user/pulls`, which return 404 on this Gitea deployment. As a result, the central work view degrades to empty lists even though `/repos/issues/search` returns real cross-repository work. Mobile currently only collapses the desktop grid and puts context/AI panels before actionable items. Historical issues and recent commits contain no supported-search or mobile action-inbox implementation. ## User flow Open the dashboard on a phone, see a prioritized **My Work** queue immediately below the header, filter All/Issues/PRs, and tap a full card to open the correct forge item. Successful data remains visible if a later refresh fails. ## Acceptance criteria - Use supported Gitea search APIs to return real assigned/open issues and pull requests without relying on `/user/issues` or `/user/pulls`. - Normalize repository identity, URL, labels, assignees, and updated time for cross-repository items. - Render My Work before auxiliary panels on narrow screens, with All/Issues/PRs filters and 44px tap targets. - Rank priority-labelled then assigned work deterministically and distinguish duplicate item numbers by repository. - Preserve the last successful queue on refresh failure and mark it stale. - Add behavioral tests, including endpoint selection, deterministic ranking/rendering, and mobile layout semantics.
timmy was assigned by rockachopa 2026-08-06 15:19:22 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#115
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?