CiviCRM Feature Requests

These are features that would make our clients lives (and ours!) much easier and would improve the CiviCRM core functionality. Some of this may already be on a future roadmap and/or already in place for 2.0.

CiviCRM Core

• Go-to (or view) contact button for quick search (like in 2.0 sandbox) CRM-2622 - Fixed in 2.1
• Searching by activity subject
• Searching by county
• Editing completed activities
• Standardize "more actions" with most common actions in every component
• A way to add organization name, employer name into mailing labels
• Search by email in "quick search" and "find contacts"
• Profiles to also work as action alert forms (similar in functionality to Drupal survey module).
  • Ability to specify a recipient(s) as To:, CC:, BCC:.
  • Ability to set default values for forms, textareas, etc.
  • Ability to track messages sent, bounced, opened, etc.
• Schedule activity reminder emails
• Less margin of error for source field (maybe a drop down menu).
• Voter ID and political info
  • Be able to look up a person's legislative districts quickly and easily, maybe automatically
  • Like mapping
• Simplify contact information. "Billing, Home, Main, Other", "Work, Phone, Mobile, Fax, Pager" is confusing for users importing their data.
• More easily groups custom data fields
  • When you create a new group of custom fields as a tab, it would be great to allow new groups of custom fields that are inline to be in that tab, not the summary tab by default.
  • Now any custom field will appear as a list within that tab.
• Profiles
  • Names of profiles to differentiate between internal vs. display name
  • TinyMCE or text editor for profiles intro/help fields

Reporting

• Intuitive interface for Search Builder geared to "non-techies." Perhaps an iTunes-esque query builder for custom reports.
  (i.e. The user shouldn't have to know what all operations mean or know the Tag IDs.)
• Allow searching by activity type/subject (and multiple) in Search Builder.
• Allow searching by "has not given money", "has never been a member", "gave last year but not this year."
• Searching by "New contacts within the last x months that are tagged Volunteer."
• Visuals. (i.e. graphs, charts, etc. on CiviContribute homepage).
• Provide a "Custom Reports" tab that would allow developers to include custom queries.

CiviContribute

• Contributions to distinguish between 2 $50 donations and one $100 donation (i.e. cumulative donations). (in 2.0)
• Not refreshing contribution forms when selecting type.
• Graphs/charts (see reporting above).

CiviMail

• Editable e-mail subscribe pages (i.e. add profiles like contribution/event registration pages).
• Not require both text and html inputs.
• Being able to add custom tokens to email. I.e.If I send an email to constituents in a certain legislative district being able to input: Dear
  (contact_name) please contact (contact's_ legislator)
  about nuclear waste dumping. His contact info is: (xyz)
  etc.....

CiviGrant

• Be able to use broad date ranges. For example, grant decision date is spring of 2008 (or quarter)
• Tab should just be for organizations (individuals/households make contributions). But organization contacts should have both contributions and grants tab because they can give both.
• "Submitted" not "received" date for application.
• "Money received" date not "transfer date."
• Under "find grants" grant report submitted option not "received"
• Admin CIVICRM - can't customize CiviGrant (like grant types, states, etc.) in sandbox & beta 5
• Amount granted and amount total seems redundant. Instead: amount requested and amount received
• Application due date instead of "app received date."
• Application due date & Grant report due dates have to show up under scheduled activities.
• You can put rationale in notes; consolidate the two.
• Keep headings consistent with grant page to search page.
• App due date is first.
• Change "number of grant" header to the following columns:
  $ month-to-date, $ year-to-date (i.e. how is our fundraising going not by number of grants but by number of $s).

CiviEvent

• Better integration with Drupal calendar module
• Easier to manage events not necessarily participants.
  • I.e easily run list of events (now if you search by event type, you get list of participants).
• Create a Drupal node for event registration page or add simple text editor for description/summary to add images, links, etc. (same with all civi pages).
• Not refreshing event info form when selecting event type.

CiviMember

• Quick searches and/or additional columns to denote, people expiring next month, this month, expired year to date, etc.
• Not requiring membership type be tied to an organization contact in your db. Maybe make it a setting?

CiviPhonebank

• Easier UI to be able to quickly add activity, notes, contributions, etc.