Repository navigation
feat(issues): report an issue with a screenshot, and an Issues panel that opens a prefilled GitHub issue - #168
Merged
Merged
Conversation
… the assistant's view actions
…ervice always accepts, and the tests The first commit added the account and view in four copies and shipped no tests. The view now sends the bare path (a query string can hold a reset token), no non-uuid page id (the service would refuse the whole run), and open_panel expands a hidden sidebar.
…that opens a prefilled GitHub issue
…and a screen share that always stops issuesApi re-implemented fetch and so skipped the client's session refresh and revocation report; it now goes through api.get/post/patch. The row type is the table's snake_case row (the camelCase twins were never sent), so the GitHub URL builder and the panel read fields directly. A capture whose play() or toBlob() failed left the screen shared; the tracks stop in finally. The guessed alias exports and the lint suppression are gone. The GitHub URL test now builds from a full row with a workspace, a reporter and a screenshot path, and checks none of them reaches the issue; the drop order (errors first, then the description) has its own two tests.
…column, and a dialog heading Checked in the browser: the panel repeated the sidebar's "Issues" title, and a side-by-side list and detail left about 120px to each in the sidebar. The panel now shows the list, or the picked report with a way back. The dialog gets the visible heading other dialogs carry, and the redaction preview shows only when redaction changed the text.
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
…a copy per file SonarCloud failed #166 at 3.7 % duplicated new lines (gate 3 %): the same 11-line shim sat in both AI view tests.
… feat/ai-issues-ui
…torage shim in the tests
|
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.
Users can report a problem from inside osionos (Help › Report an issue, the Issues rail item, or the assistant), with a screenshot. Admins triage the reports and open a prefilled GitHub issue from them.
Why
User request (2026-10-25): an Issues component in the Workbench rail, a "Report an issue" action with screenshots, a prefilled GitHub issue that a person submits, and captured frontend errors for developers.
Depends on:
What changed
ReportIssueDialog:getDisplayMedia, only on click, and the tracks stop on every path), a picked file or a paste; PNG, JPEG or WebP only, ≤5 MB, uploaded through the existing page-media path;IssuesPanel(Workbench rail):useIsAdmin) also get the All scope, status triage, "Open GitHub issue" and a link field that only acceptsgithub.com/<owner>/<repo>/issues/<n>.buildGithubIssueUrl(C222): the issue carries the report's text, route kind, app version, browser and errors, and never the screenshot URL, the workspace or the reporter. It stays ≤8000 characters by dropping errors first, then cutting the description.errorRing(C223): the last 20error/unhandledrejectionmessages, redacted, cut to 500 characters. It runs only for a platform moderator or above, or with developer mode on.open_issue_reportview action.issuesApigoes through the sharedapiclient, so session refresh and revocation apply.Before / after
Offline seed workspace, Vite dev server, 1280×820. Develop has no Issues rail item and no Report entry in Help (the rail goes Problems → Conversations).
The browser check found two layout defects, fixed in
cc4af9748:Evidence
typecheck,lintandtest-canvasare green oncc4af9748: 4010/4010.tests/canvas/issues-*.test.tsholds 16 tests. Revert proofs:Trade-offs
The screenshot reaches staff through the existing media path, so a report holds a capability path rather than bytes. It is never put in the public GitHub issue; the issue says a screenshot exists in osionos.