Why
The browser can file, discuss, label, assign, close, and reopen issues and changes,
but it cannot correct what one of them says. Fixing a typo in an issue needs the
CLI (vole issue edit), and a change request’s title or description cannot be
edited from either surface after it is opened. Someone who only uses the web is
stuck with the first draft, and a review that starts from an unclear description
stays unclear.
Scope
- Add an edit page for an issue’s title and description in the browser.
- Add the same page for a change request’s title and description.
- Offer it to the item’s author and to a maintainer, the same rule as the other item writes and the pre-receive path.
- Write through the metadata layer so the file format and validation stay in one place, and record the action in the audit log.
- Cover the two pages and the refusals with a server test.
- Mention the browser edit in the issue and change-request docs.
Acceptance criteria
- An author or maintainer sees an Edit control on an issue and on an open or closed change, and can change the title and description from it.
- A signed-in account that is neither the author nor a maintainer gets a refusal.
- The edited record is what the page, the list, and the metadata branch show afterwards.
- The existing comment and review state is untouched by an edit.