Operators need an audit trail for where files came from, where they went, and why imports failed or were skipped.
Proposed change
Add a dedicated Import History page and API filters.
Scope
History columns for source, target, import type, SAB job name/category/nzo_id, size, status, timestamps, and error.
Filters for imported, failed, skipped, manual batch, SAB, date range, and text search.
Links from queue items to history records.
Retention/pagination controls.
Acceptance criteria
Every attempted import creates a history record.
History is paginated and filterable.
Errors are readable without exposing API keys or secrets.
UI shows enough detail to troubleshoot bad imports.
## Problem
Operators need an audit trail for where files came from, where they went, and why imports failed or were skipped.
## Proposed change
Add a dedicated Import History page and API filters.
## Scope
- History columns for source, target, import type, SAB job name/category/nzo_id, size, status, timestamps, and error.
- Filters for imported, failed, skipped, manual batch, SAB, date range, and text search.
- Links from queue items to history records.
- Retention/pagination controls.
## Acceptance criteria
- Every attempted import creates a history record.
- History is paginated and filterable.
- Errors are readable without exposing API keys or secrets.
- UI shows enough detail to troubleshoot bad imports.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Operators need an audit trail for where files came from, where they went, and why imports failed or were skipped.
Proposed change
Add a dedicated Import History page and API filters.
Scope
Acceptance criteria