feat(tickets): add a basic (barren) React tickets list page - #5181
Open
wescopeland wants to merge 3 commits into
Open
feat(tickets): add a basic (barren) React tickets list page#5181wescopeland wants to merge 3 commits into
wescopeland wants to merge 3 commits into
Conversation
Contributor
Greptile SummaryAdds the initial authenticated React ticket-list page.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Reviews (2): Last reviewed commit: "test: add coverage" | Re-trigger Greptile |
Jamiras
approved these changes
Aug 20, 2026
Jamiras
left a comment
Member
There was a problem hiding this comment.
It's hard to tell whether functionality is intentionally or unintentionally missing (like tooltips).
The basic grid functionality and links all seem to work. I couldn't figure out how to make the status grouping headers appear.
Did not look at code.
Jamiras
approved these changes
Aug 26, 2026
wescopeland
force-pushed
the
stack/tickets/4-tickets2-page
branch
from
August 26, 2026 23:16
0efed77 to
6f66a28
Compare
wescopeland
force-pushed
the
stack/tickets/4-tickets2-page
branch
from
August 31, 2026 20:22
6f66a28 to
aa96064
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR builds the initial React tickets index page. There is a lot missing from this page - intentionally - to narrow this branch's scope. Notably, there are no UI controls of any kind on the page. Mobile is also lacking. This branch's changes are foundational work for the UI, just to get something workable on the screen that can be built on top of.
http://localhost:64000/tickets2
http://localhost:64000/tickets2?filter[status]=all
http://localhost:64000/tickets2?page[number]=2
The UI here already has slight differences from our conventional datatables, even though it very much is a datatable:
Status is represented with an a11y-aware Linear-like glyph:
Eventually, I'd like to see these statuses not only apply to tickets which a dev needs to jump on, but also general "issues" like UWC reports, etc. Eventually, the "Ticket Manager" may become an "Issue Manager", and users will have an "inbox" that shows them the current status of all their issues.