Backend Issue 8: Add Human Issue List And Read APIs #9

New Issue

Closed

opened 2026-05-19 02:27:59 -05:00 by null · 0 comments

null commented

2026-05-19 02:27:59 -05:00

Owner

Goal

Allow authenticated Pipeline users to view cached Forgejo issues through Pipeline APIs.

Suggested Endpoints

GET /api/v1/forgejo/issues
GET /api/v1/forgejo/issues/{issue_id}

Acceptance Criteria

Users can list issues by repository id, state, label text, assignee text, and search text.
Users can read one cached issue by id.
Users cannot read issues from another organization.
Pull requests are excluded from issue list responses in MVP.
Responses never include connection tokens.
Tests cover allowed access, forbidden cross-org access, filters, and pagination.

Out Of Scope

Board-scoped repository links, Issue closing, Agent routes, Frontend UI.

## Goal Allow authenticated Pipeline users to view cached Forgejo issues through Pipeline APIs. ## Suggested Endpoints - `GET /api/v1/forgejo/issues` - `GET /api/v1/forgejo/issues/{issue_id}` ## Acceptance Criteria - Users can list issues by repository id, state, label text, assignee text, and search text. - Users can read one cached issue by id. - Users cannot read issues from another organization. - Pull requests are excluded from issue list responses in MVP. - Responses never include connection tokens. - Tests cover allowed access, forbidden cross-org access, filters, and pagination. ## Out Of Scope - Board-scoped repository links, Issue closing, Agent routes, Frontend UI.