@@ -52,20 +52,22 @@ Required variables:
|
||||
- Created issues must upload the selected rendered agent file as a Gitea issue asset. Supported template variables in agent content are `{{git}}`, `{{repo}}`, `{{workspace}}`, `{{url}}`, `{{baseUrl}}`, `{{profile}}`, and `{{issue}}`.
|
||||
- Newly created issues must use the selected labels.
|
||||
|
||||
## Open Issues
|
||||
## Issues
|
||||
|
||||
- Open Issues owns existing issue browsing and follow-up comments.
|
||||
- The primary Open Issues panel lists recent issues ordered by creation time.
|
||||
- Issues owns existing issue browsing and follow-up comments.
|
||||
- The primary Issues panel lists recent issues ordered by creation time.
|
||||
- The `Only current repo` checkbox defaults to checked and limits the table to the active URL's linked Gitea repo.
|
||||
- Turning off `Only current repo` loads recent issues from all repos already loaded in the extension.
|
||||
- The status dropdown defaults to `Open` and supports `Open`, `Closed`, and `Open + Closed`.
|
||||
- Selecting an issue shows a direct Open in Gitea link, editable issue subject/content/label fields, issue attachments, direct attachment upload controls, comment chain, and a comment form for text, additional screenshots, and file attachments.
|
||||
- Saving selected issue edits must use the repo identity from the selected Open Issues row, include Gitea's current issue content version when available, verify the saved subject/content with a readback before reporting success, save labels through Gitea's issue labels endpoint, and must not fall back to the active tab's repo.
|
||||
- Status filtering uses `Open` and `Closed` checkboxes as a multiselect. The default is `Open` checked.
|
||||
- The label filter defaults to empty and filters the visible issue rows by a selected known label.
|
||||
- Selecting an issue shows a direct Open in Gitea link, a Send to Codex button that currently logs the selected issue payload, editable issue subject/content/label fields, issue attachments, direct attachment upload controls, comment chain, and a comment form for text, additional screenshots, and file attachments.
|
||||
- Clicking the selected issue row again or clicking the detail close control closes the selected issue detail panel without deleting or changing the issue.
|
||||
- Saving selected issue edits must use the repo identity from the selected Issues row, include Gitea's current issue content version when available, verify the saved subject/content with a readback before reporting success, save labels through Gitea's issue labels endpoint, and must not fall back to the active tab's repo.
|
||||
- Issue comments should upload screenshots/files as issue assets first, then create a comment containing links to those attachments.
|
||||
- Additional selected-issue screenshots/files can also be uploaded directly as issue assets without creating a comment.
|
||||
- Existing issue attachments can be deleted from the selected issue.
|
||||
- Existing issue rows can delete the issue. Issue labels are edited in the selected issue form. Deletion must require confirmation.
|
||||
- Typing in Add Issue, selected issue edit fields, Open Issues comments, or Agents editor fields must not blur the focused control.
|
||||
- Typing in Add Issue, selected issue edit fields, Issues comments, or Agents editor fields must not blur the focused control.
|
||||
|
||||
## URL Management
|
||||
|
||||
|
||||
Reference in New Issue
Block a user