Custom Fields: Implement tests regarding changing of name and type #198

Open
opened 2025-11-10 16:36:37 +01:00 by simon · 1 comment
Owner

Description

Changing name and/or type of a custom field can lead to side effects.

  • On name change: should the slug also reflect that name change?
  • Should a type change after creation be allowed at all?
  • On type change: What happens to previously assigned custom fields and their (typed) values?
    • Should we support a type migration (e.g. mail to String) where applicable?
    • Should only certain type conversions be possible?

Acceptance criteria

  • Decisions on the handling of name and type changes are documented here
  • Decisions are implemented as tests and implemented accordingly
## Description Changing name and/or type of a custom field can lead to side effects. - On name change: should the slug also reflect that name change? - Should a type change after creation be allowed at all? - On type change: What happens to previously assigned custom fields and their (typed) values? - Should we support a type migration (e.g. mail to String) where applicable? - Should only certain type conversions be possible? ## Acceptance criteria - [x] Decisions on the handling of name and type changes are documented here - [ ] Decisions are implemented as tests and implemented accordingly
simon added this to the I can add custom fields milestone 2025-11-10 16:36:37 +01:00
simon added the
question
M
labels 2025-11-10 16:36:37 +01:00
Owner

@moritz and I had a talk and we decided the following

  • display name can be changed
  • slug cannot be changed
  • type cannot be changed
@moritz and I had a talk and we decided the following - display name can be changed - slug cannot be changed - type cannot be changed
moritz added this to the Sprint 9: 20.11 - 11.12 project 2025-11-20 11:58:12 +01:00
rafael removed this from the Sprint 9: 20.11 - 11.12 project 2025-12-01 20:30:43 +01:00
simon changed title from Custom Fields: Define consequences of changing name and type to Custom Fields: Implement tests regarding changing of name and type 2025-12-01 20:31:04 +01:00
Sign in to join this conversation.
No project
No assignees
2 participants
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#198
No description provided.