add-ideas/govoplan-campaign
1
0
Fork 0
Code Issues 49 Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature] Replace recipient entry form with a full recipient-data editing panel #67

New Issue
Closed
opened 2026-07-14 20:08:41 +02:00 by zemion · 7 comments
zemion commented 2026-07-14 20:08:41 +02:00
Owner
Copy Link

Problem / User Need

Recipient entering/editing should become a structured editing panel that can edit sender and recipient address data in one place: from, to, cc, bcc, multiple addresses, merge toggles, and row fields.

Acceptance Criteria

  • A recipient-data editing panel exposes the same editing logic as one row in Recipients.
  • The panel supports from, to, cc, bcc, multiple addresses, and merge/toggle behavior.
  • Sender and recipient dataset editing becomes one coherent page/table rather than split forms.
  • Changes remain auditable and validation errors are attached to the exact edited field.

Notes / Decisions

Needs UX/data-model design before implementation because it changes the recipient editing surface substantially.

## Problem / User Need Recipient entering/editing should become a structured editing panel that can edit sender and recipient address data in one place: from, to, cc, bcc, multiple addresses, merge toggles, and row fields. ## Acceptance Criteria - A recipient-data editing panel exposes the same editing logic as one row in Recipients. - The panel supports from, to, cc, bcc, multiple addresses, and merge/toggle behavior. - Sender and recipient dataset editing becomes one coherent page/table rather than split forms. - Changes remain auditable and validation errors are attached to the exact edited field. ## Notes / Decisions Needs UX/data-model design before implementation because it changes the recipient editing surface substantially.
zemion commented 2026-07-15 00:37:26 +02:00
Author
Owner
Copy Link

Okay, we have now tow pages, one "Sender & Recipients", and one "Recipient data". The top panels for "Campaign sender" and "Global recipient headers" can stay; after that, the two tables from the two pages become merged. For that, the second column "Recipient(s)" is changed so that it displays one recipient address, plus indicators for +1, +2 CC, +1 BCC, and so on. This column gets an editing pen that opens an overlay where recipients (addresses for now) can be added to the available fields (From, To ,CC, ...), the availability of which is determined by the campaign global toggles. Usually, multiple entries are allowed, and they can merge with a global value or overwrite it (the toggle usually usde might be extended as to provide two labels - one describing the meaning of "off/no/false", in our case overwrite, the other "on/yes/true", meaning in our case merge). The modelling is similar to the now existing recipient table from "Sender & Recipients", just not displayed as columns, but rather rows in the overlay.

Okay, we have now tow pages, one "Sender & Recipients", and one "Recipient data". The top panels for "Campaign sender" and "Global recipient headers" can stay; after that, the two tables from the two pages become merged. For that, the second column "Recipient(s)" is changed so that it displays one recipient address, plus indicators for +1, +2 CC, +1 BCC, and so on. This column gets an editing pen that opens an overlay where recipients (addresses for now) can be added to the available fields (From, To ,CC, ...), the availability of which is determined by the campaign global toggles. Usually, multiple entries are allowed, and they can merge with a global value or overwrite it (the toggle usually usde might be extended as to provide two labels - one describing the meaning of "off/no/false", in our case overwrite, the other "on/yes/true", meaning in our case merge). The modelling is similar to the now existing recipient table from "Sender & Recipients", just not displayed as columns, but rather rows in the overlay.
zemion commented 2026-07-15 01:06:56 +02:00
Author
Owner
Copy Link

Codex State: ready

Summary

  • Consolidated the sender/global-recipient controls and inline recipient table into one recipient-data editing surface.
  • Added a selected-recipient editor panel for ID, name, email, active state, from, reply-to, to, cc, bcc, and merge toggles, reusing the existing draft update path.
  • Fixed the WebUI fallback so per-recipient To editing is enabled when allow_individual_to is omitted, matching generated campaign defaults.

Changed Files

  • webui/src/features/campaigns/RecipientDataPage.tsx
  • webui/src/styles/campaign-workspace.css

Verification

  • GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.

Next / Blocked

  • Visual/UX review in the running app before closing; the issue is intentionally left open.

Suggested status label: status/ready

## Codex State: ready ### Summary - Consolidated the sender/global-recipient controls and inline recipient table into one recipient-data editing surface. - Added a selected-recipient editor panel for ID, name, email, active state, from, reply-to, to, cc, bcc, and merge toggles, reusing the existing draft update path. - Fixed the WebUI fallback so per-recipient To editing is enabled when allow_individual_to is omitted, matching generated campaign defaults. ### Changed Files - `webui/src/features/campaigns/RecipientDataPage.tsx` - `webui/src/styles/campaign-workspace.css` ### Verification - `GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.` ### Next / Blocked - Visual/UX review in the running app before closing; the issue is intentionally left open. Suggested status label: `status/ready`
zemion commented 2026-07-15 02:02:39 +02:00
Author
Owner
Copy Link

Codex State: ready

Summary

  • Restored the two collapsible global sender/header cards and moved per-recipient address editing into a Recipient(s) column overlay.

Changed Files

  • webui/src/features/campaigns/RecipientDataPage.tsx
  • webui/src/styles/campaign-workspace.css

Verification

  • GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.

Next / Blocked

  • Visual review in the running app; issue left open until confirmed.

Suggested status label: status/ready

## Codex State: ready ### Summary - Restored the two collapsible global sender/header cards and moved per-recipient address editing into a Recipient(s) column overlay. ### Changed Files - `webui/src/features/campaigns/RecipientDataPage.tsx` - `webui/src/styles/campaign-workspace.css` ### Verification - `GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.` ### Next / Blocked - Visual review in the running app; issue left open until confirmed. Suggested status label: `status/ready`
zemion commented 2026-07-15 02:20:58 +02:00
Author
Owner
Copy Link

Codex State: ready

Summary

  • Merged recipient field values and attachment editing into the Sender & Recipients table after the Active column, removed the separate Recipient data navigation/page, and replaced the overlay merge segmented control with the standard toggle.

Changed Files

  • webui/src/features/campaigns/RecipientDataPage.tsx
  • webui/src/styles/campaign-workspace.css
  • webui/src/features/campaigns/CampaignWorkspace.tsx
  • webui/src/layout/SectionSidebar.tsx
  • webui/src/features/campaigns/RecipientDetailsPage.tsx

Verification

  • GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.

Next / Blocked

  • Visual review in the running app; issue left open until confirmed.

Suggested status label: status/ready

## Codex State: ready ### Summary - Merged recipient field values and attachment editing into the Sender & Recipients table after the Active column, removed the separate Recipient data navigation/page, and replaced the overlay merge segmented control with the standard toggle. ### Changed Files - `webui/src/features/campaigns/RecipientDataPage.tsx` - `webui/src/styles/campaign-workspace.css` - `webui/src/features/campaigns/CampaignWorkspace.tsx` - `webui/src/layout/SectionSidebar.tsx` - `webui/src/features/campaigns/RecipientDetailsPage.tsx` ### Verification - `GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.` ### Next / Blocked - Visual review in the running app; issue left open until confirmed. Suggested status label: `status/ready`
zemion commented 2026-07-15 02:29:06 +02:00
Author
Owner
Copy Link

Codex State: ready

Summary

  • Fixed the recipient address overlay row actions to reuse colored DataGrid action buttons, removed the redundant edit action, kept newly added blank address rows visible while editing, and extended the shared ToggleSwitch with active/inactive state labels used for Overwrite/Merge.

Changed Files

  • webui/src/features/campaigns/RecipientDataPage.tsx
  • webui/src/styles/campaign-workspace.css
  • ../govoplan-core/webui/src/components/ToggleSwitch.tsx

Verification

  • GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.

Next / Blocked

  • Visual review in the running app; issue left open until confirmed.

Suggested status label: status/ready

## Codex State: ready ### Summary - Fixed the recipient address overlay row actions to reuse colored DataGrid action buttons, removed the redundant edit action, kept newly added blank address rows visible while editing, and extended the shared ToggleSwitch with active/inactive state labels used for Overwrite/Merge. ### Changed Files - `webui/src/features/campaigns/RecipientDataPage.tsx` - `webui/src/styles/campaign-workspace.css` - `../govoplan-core/webui/src/components/ToggleSwitch.tsx` ### Verification - `GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.` ### Next / Blocked - Visual review in the running app; issue left open until confirmed. Suggested status label: `status/ready`
zemion commented 2026-07-15 02:30:29 +02:00
Author
Owner
Copy Link

Codex State: ready

Summary

  • Filtered merged recipient-data columns so only editable recipient-specific columns are shown: field columns now require can_override, and the attachments column is only shown when an individual attachment source exists.

Changed Files

  • webui/src/features/campaigns/RecipientDataPage.tsx

Verification

  • GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.

Next / Blocked

  • Visual review in the running app; issue left open until confirmed.

Suggested status label: status/ready

## Codex State: ready ### Summary - Filtered merged recipient-data columns so only editable recipient-specific columns are shown: field columns now require can_override, and the attachments column is only shown when an individual attachment source exists. ### Changed Files - `webui/src/features/campaigns/RecipientDataPage.tsx` ### Verification - `GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui passed.` ### Next / Blocked - Visual review in the running app; issue left open until confirmed. Suggested status label: `status/ready`
zemion commented 2026-07-15 02:41:12 +02:00
Author
Owner
Copy Link

Codex State: done

Summary

  • Confirmed by user; merged recipient editing implementation accepted.

Verification

  • Previously verified with GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui.
## Codex State: done ### Summary - Confirmed by user; merged recipient editing implementation accepted. ### Verification - `Previously verified with GOVOPLAN_WEBUI_MODULE_PACKAGES=@govoplan/campaign-webui npm run build in govoplan-core/webui.`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/deployment
Deployment, release, operations, or runtime packaging.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/approvals
GovOPlaN Approvals module behavior or integration.
module/assets
GovOPlaN Assets module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/booking
GovOPlaN Booking module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/certificates
GovOPlaN Certificates module behavior or integration.
module/committee
GovOPlaN Committee module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/consultation
GovOPlaN Consultation module behavior or integration.
module/contracts
GovOPlaN Contracts module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/docs
GovOPlaN documentation layer behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/facilities
GovOPlaN Facilities module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
module/grants
GovOPlaN Grants module behavior or integration.
module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/inspections
GovOPlaN Inspections module behavior or integration.
module/issue-reporting
GovOPlaN Issue Reporting module behavior or integration.
module/learning
GovOPlaN Learning module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/procurement
GovOPlaN Procurement module behavior or integration.
module/records
GovOPlaN Records module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/resources
GovOPlaN Resources module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/transparency
GovOPlaN Transparency module behavior or integration.
module/web
GovOPlaN public website, product page, or publication content.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/module-roadmap
Created from GovOPlaN module and integration roadmap planning.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
area/api
area/webui
codex/needs-human
module/campaign
priority
p2
status
triage
type
feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-campaign#67
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?