- Ya
- 28 Agosti 2026, 05:51 UTC
- Mwandishi
- Kamo
- Ahadi ya
- a5ab3f5
Right-aligned on the "What are you reporting?" row, off every time the window opens — it starts a session on a machine holding cluster credentials, and a switch that remembered its last position would eventually send something nobody meant to send. Submitting with it on hands the report straight over: In Progress, and read by the operator who sent it. Drawn only for a holder of MANAGE_SYSTEM_BUGS, read from the server-resolved PlatformRightsContext — checkRight is the TENANT rights spine and cannot answer for a platform right at all, so asking it would have hidden the switch from every platform administrator. That is chrome either way: SecurityService's endpoint sits under a class-level @RequirePlatformRight and refuses anybody else with a 403. The request carries a bug id and NOTHING ELSE. The form has no prompt box, no model picker and no screenshot picker, so the server chooses all of them; assembling a payload here would have put those choices in the browser, where the member holding the right could edit them. The hand-off runs after the uploads, not beside them — the dispatch reads whatever is attached at the moment it runs, and a session started early would be working from half a report. A dispatch that fails still applies its status, so the report is In Progress by the time the button is pressed again and a reporter may only edit one that is still New: the window remembers what it last wrote and skips the redundant re-save, or the retry would report that a saved report could not be saved and never re-attempt the thing that actually failed.