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

Improvements to the findability of events

    Details

    • Type: Improvement
    • Status: Won't Do
    • Priority: Minor
    • Resolution: Won't Do
    • Affects Version/s: 4.6.4
    • Fix Version/s: Unscheduled
    • Component/s: CiviEvent
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      User and Admin Doc
    • Funding Source:
      Needs Funding

      Description

      With the advent of the recurring events functionality it is now a simple task to create many very similar events. As an example on a current project that I'm working on we have created well over 1000 events. However the tools to list, find, sort and filter those events remain very basic. I think there are two key elements to improving this:

      1. The current 'Manage Events' listing displays limited information about any given event. Whilst the ID number of an event is shown, it needs to be in a separate field such that the listing can be sorted by ID. It would also be valuable to include a listing column to identify whether an event was a parent or child event, with a link to a display listing all of the child events of a given parent. The default listing sort order, which I think is currently alphabetical based on the name of the event, is also unhelpful. A default listing based on either event start date or ID number would make much more sense, and ideally the default could be selectable by the site administrator.

      2. A new 'Find Events' search tool is needed whereby events can be found based on any of the fields used for events.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              upperholme Graham Mitchell
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: