local-it/mitgliederverwaltung
2
3
Fork 0
Code Issues 51 Pull requests 13 Projects 1 Releases Packages 1 Activity Actions

Implement UI fields to mock payment concept #226

New issue
Closed
opened 2025-12-01 21:19:00 +01:00 by simon · 0 comments
simon commented 2025-12-01 21:19:00 +01:00
Owner
Copy link

Description

Following #210

We want to implement the fields in the member edit view to test whether this reflects the test organizations view on how they want to manage the membership fee/contribution data

Acceptance criteria

  • Fields only exist in UI
  • There is a hint informing users about the non-functional implementation and asking for feedback

External or internal Dependencies

## Description Following #210 We want to implement the fields in the member edit view to test whether this reflects the test organizations view on how they want to manage the membership fee/contribution data <!--- Describe the goal and desired output ---> <!--- Add the estimated effort as label ---> ## Acceptance criteria - [x] Fields only exist in UI - [x] There is a hint informing users about the non-functional implementation and asking for feedback ## External or internal Dependencies <!-- List any dependencies --->
simon added this to the Sprint 9: 20.11 - 11.12 project 2025-12-01 21:19:31 +01:00
simon added a new dependency 2025-12-01 21:19:40 +01:00
#210 [FEATURE]: Payment Concept
simon added the
enhancement
 label 2025-12-01 21:19:52 +01:00
simon added this to the Membership Payments milestone 2025-12-01 21:22:05 +01:00
moritz self-assigned this 2025-12-02 15:58:04 +01:00
moritz removed their assignment 2025-12-03 13:54:40 +01:00
rafael was assigned by moritz 2025-12-03 13:54:41 +01:00
moritz removed a dependency 2025-12-03 14:42:59 +01:00
#210 [FEATURE]: Payment Concept
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
renovate/renovate-renovate-42.x
renovate/mix-dependencies
perform-migration-on-startup
feature/196_search_custom_fields
feature/220_ui_issues_2
sidebar
renovate/major-postgres
feature/223_member_checkbox
renovate/major-mix-dependencies
renovate/postgres
renovate/ghcr.io-sebadob-rauthy-0.x
persist-sort-order
docs/210_payment-concept
feature/151_roles_permissions_docs
manual_renovate_update
feature/#158-polish-README
feature/128_playwright_a11y_test
feature/119_member_user_relation_refactor
feature/119_user_as_member
feature/backpex-migration
feature/backpex_translation
feature/39_account_ressource
feature/74_memberfields
validation
feature/36_add_primerlive
Clear current reference
No results found.
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
high priority

   
invalid

Something is wrong

  
L

5 h

  
low priority

   
M

3 h

  
medium priority

   
needs refinement

   
question

More information is needed

  
S

1 h

  
UX research

   
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
question
S
UX research
wontfix
Milestone
Clear milestone
No items
No milestone
Membership Payments
Projects
Clear projects
No items
No project
Sprint 9: 20.11 - 11.12
Assignees
Clear assignees
No assignees
rafael
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: local-it/mitgliederverwaltung#226
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?