Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-3547

Naming control for participant statuses

    Details

    • Type: Improvement
    • Status: Done/Fixed
    • Priority: Minor
    • Resolution: Fixed/Completed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.2.0
    • Component/s: CiviEvent
    • Labels:
      None

      Description

      As part of supporting an RSVP work-flow in CiviEvent, administrators want to be able to modify the Labels used for "reserved" participant statuses (e.g. change "Registered" to "Yes, I'm coming"). As far as i can tell, none of our code is keyed off of the option_value.label strings - so we can open that field for editing as follows:

      • When editing option value records in the participant_status option group, for reserved records, allow editing of the Label field.

      NOTE: This means that 2 fields are now editable for reserved option value rows in this option group: the "Counted" field and the "Label". Please test a normal online registration flow after changing the label for "Registered" to verify that there are no unexpected results.

      ---- Original Post ----
      Feature request mentioned here: http://forum.civicrm.org/index.php?topic=4741.0

      Allow a CiviCRM administrator to configure the names of participant statuses within Administer CiviCRM. This will allow for more customization and combined with this feature request: http://issues.civicrm.org/jira/browse/CRM-3546 be a great way for users to set their own status on an event registration page with a profile that includes the participant status field.

      thanks

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                shot Piotr Szotkowski
                Reporter:
                dharmatech Dharmatech
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: