Skip to end of metadata
Go to start of metadata

Please post detailed descriptions of your requirements for the future releases of CiviEvent on this page. Be sure and review the Phase 1 features, as well as the CiviEvent section of the 2.1 Roadmap as you think about your use cases.

Scheduled for 2.1

Refer to the CiviEvent section of the 2.1 Roadmap

Candidate Features for Future Releases

  • RSVP-style Event Registration
  • From Joe Murray's post: "From my perspective, the advantage of using a price set is that it allows a single place to administer the fees for several events. One can add and edit fine, but when trying to delete an option, a message is displayed indicating one needs to go to each of the events using the price set to delete the option. This is counterintuitive. Even when all participants were removed from the events it wouldn't let the price option be deleted. If there are current registrants for active events that are using the price option, then I think it is reasonable to prevent deletion until the event is no longer active, or those registrations have been deleted. When no one has subscribed using that price option, however, at most, a warning message should be displayed saying that the price option is currently in use."
  • Price set data model overhaul (probably moving to custom field / custom data model). The new model should allow participant export to output each price set field as a separate column (so folks can easily calculate counts etc.).
  • Generate and store unique invoice numbers for pay later registrations, and include it in thank you email sent to users (eg via a token replacement scheme).
  • Configure event fees for specific Participant or ACL Roles. Use cases include:
    • "member" vs. "non-member" event pricing
    • allow "free" registration of speakers, volunteers etc. to a paid event
  • Configure Participant Roles which are not counted against the maximum number of participants. Primary use case is to allow registration of speakers, volunteers and others who are not supposed to be counted against the participant limit.
  • Create Recurring Events:
    • With frequency + duration - Every Monday at 7pm for 12 weeks
    • With a set of dates - April 7, April 10, April 14, April 17
  • Event creator can choose to include a CAPTCHA element in the registration form.
  • Extend the data model to allow entities in the CiviCRM DB to "own" an event (e.g. and Organization, Group or Individual). This has implications for permissioning and also probably means we would need a simplified "end-user" event creation wizard which hides many of the current config options.
  • Allow for nesting events. One event should be able to contain multiple other events. Ideally administrators would be able to designate certain child events as mandatory (participant automatically registered for child when registered for parent) or optional. See the first comment for more information. Participant statuses for the parent would be defined as Attended if all registered children were attended, No Show if no registered children were attended, and Partial if at least one child event was attended. Participant statuses should be independent for all children. Participant status for the parent event should be either automatic (determined based on statuses of the children) or manual (independent of children).
  • Associate an event fee with a participant role.
  • Provide a way to allow people to contribute any amount of money as they register (in addition to the event fee). Ideally there would solutions for the simple "list of event fees" mode AND for use with price sets. (http://forum.civicrm.org/index.php/topic,3243.0/topicseen.html)
  • Allow people to cancel event registration (e.g. through cancel link in registration confirmation email) - (see: http://forum.civicrm.org/index.php/topic,4571.0.html). Also look at allowing them to modify non-price-related aspects of their registration info (e.g. profile-driven participant fields).
  • In some cases, it may be desirable to allow participants to register more than once for the same event.  There should be an "allow multiple registrations" checkbox in the "Online Registration" section of the event config.

Improve fee and payment structure

  • Currently you cannot edit event fees if you record a contribution as part of the event registration process (backend). There needs to be a way to alter fees and handle the corresponding contribution record.
    • This could be structured similar to the CiviMember renewal function. In that system, one membership record has multiple contribution records associated with it, and the renewal function ensures existing contributions are not altered.
    • "Alter Fees" function would allow a person to add or modify previously selected fees. Ideally, the total due less previously associated contributions would be visible, so only the balance due (post-change) is charged. If that auto-calculate function is not easy to implement, you'd want to at least have a list of the previous contributions associated with the record (for reference) and the ability to actually enter in the amount associated with that new contribution (because it won't be the total amount).
  • Add a dropdown in CiviContribute so that you can associate a contribution with a specific event. Currently, if you create a contribution record for event fees in CiviContribute, it's not connected to the associated event. This is particularly problematic since the credit card transaction mechanism is not available within the CiviEvent/CiviMember record contribution block. The table structure already exists -- we just need the bridge built to that form.

Attendance lists

(from http://forum.civicrm.org/index.php/topic,4573.0)
"It has been suggested that being able to create attendance lists would be nice. Related would be a very lightweight mechanism to make certain changes, so that one could have a check - in desk that had the list of all registered guests with a check boxes for checked ID, accepted payment, gave badge, (etc.) that did were immediately communicated to the database without having to refresh the entire page (there also needs to be some way to notify other open pages of these changes so that one could not pick up ones materials from one person, then walk over to another person and "check in" again). Alternatively, some other fast search/modication for CiviEvent check in desks would be great. Finally, coupling this with the ability to print badges would be fantastic."

Implemented Features

  • (v2.0) Static URLs for event participant listings
  • (v2.0) Duplicate registration detection
  • (v2.0) Pay-later / pay-by-cheque
  • (v1.8) Add a close date for online registration after which participants must be registered through the backend
  • (v1.8) Import UPDATE of participants - so you can import a CSV file with attendance/status updates for an existing set of event participants. Matches participants on Event ID + Contact field(s).
Labels:
  1. Jan 08, 2007

    CA

    We'd really like to see support for multi-session events. Basically, it would be awesome if you could define an event as being a container for other events, so that people could register for the container event and be automatically registered for the children events. An example of this would be a course which has say five classes. We need to keep track of attendance for each class in a five-class series.

    Event:
    Event Dates: 1/1/07, 1/3/07, 1/5/07, 1/7/07
    Event Status: [Registered, Attended, Cancelled, No-Show, PARTIAL, IN PROGRESS] - I think you'd need two additional statuses to support this. Partial if a mixture of attendeds and no-shows after last event, in progress between first and last event. Maybe the statuses could be implemented somewhat like the membership statuses in CiviMember? 

  2. Apr 06, 2007

    Allow people to register for paid events even if they are not paying on-line. Many fundraiser type events allow you to mail a check or to pay when you arrive. So give the registree the option of deciding whether they want to register and pay online or indicate that they will pay offline.

    Maybe on the configure event fee page the last row could be the option to allow people to register by paying offline. Then add an offline payment thank you page that says mail your check to this address by this date, or pay at the door.

    Could a participant role type be assigned based on the fee level paid by the attendee? If one of the fee levels is to pay offline, then they could be assigned the role of Attendee (unpaid) and the other fee levels could be set to things like Attendee (paid) and so on.

    1. Apr 06, 2007

      I think that this could tie in nicely with the Fee Groups, currently described at http://wiki.civicrm.org/confluence/display/CRM/Event+Fee+Sets

      At this time, though, this is not a finished spec.

    2. May 05, 2008

      The "Pay Later" feature added in 2.0 covers "pay by check, pay when you arrive..." case.

      I've added fee level -> participant role linkage as a candidate feature above.

  3. Apr 24, 2007

    Would be good to be able to allow anonymous users to access iCal events listing - this way, you can automatically include your events in external calendar. This would require some special configuration option, for example: "do not check authorisation on iCal event listing view" or something along these lines.

    1. May 23, 2007

      We modified iCal listings so they are permissioned under "register for online events" - so you can grant access to anonymous users if desired. Note that only "Public" events are included in the iCal feeds.

  4. Jun 11, 2007

    Are there plans to tie event registration to Memberships?  For instance our organization runs events that are free for individuals with any of our member levels.  Non-members can pay a one-time fee to participate in the event (or they can register as a member).

    1. Jun 11, 2007

      Currently we dont have any plans to tie those two components. But a code contribution to do the above might be useful to other folks. You might want to start a forum thread on this

  5. Aug 20, 2007

    Would it be possible to allow Participants to choose available roles to be filled

    for example this could be used to fill specific volunteer slots defined using the Participant Roles feature.

    this would take them to the conformation page(or a new choose role page) where they choose in what way they will be involved in the event

     in the event setup we would have to specify what roles are public and how many slots are open for each role

  6. Dec 17, 2007

    Feature request: Integrate chapta in the event subscribe form.

  7. Dec 18, 2007

    Business logic to control what registration options or price sets are available. To begin, the business logic should be driven by membership:

        IF contact is current member:

            IF member type= associate:

                DISPLAY price set/registration options 1

            ELSE IF member type = affiliate:

                DISPLAY price set/registration options 2

        IF contact is not a members:

            DISPLAY price set/registration options 3

    Many of the organizations I work with have discounted pricing for members, and also may have different registration options based on what type of member you are -- for example a set for seminar participants, and a set for exhibitors. While all of those options can currently be exposed to members using price sets, there are no controls to ensure the individual is selecting the appropriate option, thus requiring staff review.

  8. Feb 29, 2008

    Would be nice to restrict 'max_participants' to role

    Example:
    I use CiviEvent to manage summercamps. These camps normally have 30 kids and 6 to 8 leaders.
    If i restrict the event to have at max 30 participants, the leaders are included in the total.

    It would be nice if I have the option to select the role which to count the amount of users of.

    Same goes for any other event. If a presentation can have 100 listeners, the speakers and hosts shouldn't be counted.
    Would this be possible?

  9. May 12, 2008

    In an early discussion of CiviEvent specs, Dan Robinson mentioned having a wait list. This seems like a useful feature. I would imagine signing up for the waiting list for an event should involve providing some or all of the info required to register for the event, and to be put on an ordered waiting list - a group or tag with auto-generated waiting list position that user can't edit. Event administrators who are clients of mine have indicated they would like to be able to selectively "release" those on the waiting list to enable them to register. The goal is to balance first-come first-serve for most registrants with having a good mix of people for an event in the final 10 or 20 percent of signups from prioritized selections from the waiting list.

    In terms of implementation, this would require 1) adding a counter hidden field to a signup form including profiles that is configured to add user to a group, and 2) perhaps using new acl system to let admins add contacts in waiting list group to an 'approved to register' group, and 3) restricting sign-ups after event is full to those who belong to "approved to register" group. 2) should be possible either by selecting a number to release from top of waiting list or by selecting individual contacts from a profile listing of waiting list members and submitting an 'approved to register' action on them.

  10. Sep 22, 2008

    I wanted to suggest just being able to add a quick note to the Event Calendar.  Being able to schedule events with attendees is critical, but it would be good to have a quick and easy way to just make a note of something.

    An example is "So and so will be on this radio program tomorrow at such and such time.  Tune in to see what so and so has to say."

    The wizard to create events with attendees is kind of long to go through in order to do this.


Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.