Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • E Events - archive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Development
  • Events - archive
  • Issues
  • #66

Closed (moved)
(moved)
Open
Created Dec 20, 2021 by Stoob@Stoob😺

Why are unique labels for price fields required?

This is a question not a proposal or bug report. Should a unique label for price fields be enforced (seen attached)?

Here are two use cases:

  • event registration where the price of attendance changes over time (early bird) but the event itself or the nature of the registration doesn't change

  • membership registration 'special' where prior to a certain date memberships are on sale

It seems in these cases a unique label is not necessary.

why

Edited Dec 20, 2021 by Stoob
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking