[Feature] Add address-list management UI and campaign picker #11

Closed
opened 2026-07-13 18:13:15 +02:00 by zemion · 1 comment
Owner

Goal

Add first-class UI for classical address lists after the backend/API/capability slice.

Scope

  • manage address lists within the address-book page without crowding contact CRUD
  • add/remove contacts or specific contact methods from a list
  • show read-only/disabled explanations using existing hover patterns
  • expose list sources clearly for campaign recipient-source selection
  • keep operational mixed Verteiler out of addresses and point users to Distribution Lists once available

Acceptance Criteria

  • Users can create, edit, archive, and restore address lists.
  • Users can add/remove visible contacts/contact methods from a list.
  • Campaign can distinguish address-book sources from address-list sources.
  • The UI does not introduce cross-module imports.
## Goal Add first-class UI for classical address lists after the backend/API/capability slice. ## Scope - manage address lists within the address-book page without crowding contact CRUD - add/remove contacts or specific contact methods from a list - show read-only/disabled explanations using existing hover patterns - expose list sources clearly for campaign recipient-source selection - keep operational mixed Verteiler out of addresses and point users to Distribution Lists once available ## Acceptance Criteria - Users can create, edit, archive, and restore address lists. - Users can add/remove visible contacts/contact methods from a list. - Campaign can distinguish address-book sources from address-list sources. - The UI does not introduce cross-module imports.
Author
Owner

Implemented on origin/main: users can create, edit, archive, and restore address lists and add/remove contacts or specific contact methods. Address books and lists are exposed through the capability boundary as distinct recipient-source kinds, and Campaign consumes them without cross-module imports. Addresses tests passed 14/14, Ruff passed, and the production WebUI build passed on 2026-07-20. Closing as delivered.

Implemented on `origin/main`: users can create, edit, archive, and restore address lists and add/remove contacts or specific contact methods. Address books and lists are exposed through the capability boundary as distinct recipient-source kinds, and Campaign consumes them without cross-module imports. Addresses tests passed 14/14, Ruff passed, and the production WebUI build passed on 2026-07-20. Closing as delivered.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-addresses#11
No description provided.