Future Make-it-Happen candidates

Candidate List for Make It Happen Projects

• New interface for entering batches of contributions. ( 150 - 200 hours )
• Centralizing import code and optimizing it for large imports, import api's, may be command line import script for large migration??
  ( 150 - 200 hours )
  

Large Projects

• CiviAccounts
• CiviCampaign: More Reporting. More survey questionnaire layout options. Engagement level tracking.
• Allow multiple type custom fields to be entered using front end profiles
• CiviMail Improvements
• Import API, Batch Imports, Import Extensibility and Testability

Medium Sized Projects

• Joomla ACL Integration
• Drupal Rules Module Integration / Workflow for CiviCRM
• Support for Multiple Contact Subtypes
• Logging Improvements: Rollback to previous version
• Use Profile for On Behalf Of
• Smart Groups on Contact Tabs
• Improvements to Organization Address
• Support for hierarchical custom fields
• Civi Report for searching on multiple custom data fields
• Clean URLs - for events / contribution pages/ profiles
• "Grid" batch input of new records - initially for Contributions (rough spec here), but possibly extend for:
  • New Membership
  • New Event Registration
  • New Pledge
• CiviMember
  • Allow imported / offline memberships to be renewed online
  • Membership Approval Process
  • Facilitate membership "upsell" process
  • Price sets for memberships (est 50 hours)
• CiviEvent
  • Allow people to add more information to their registration
  • Recurring Events:
    • With frequency + duration - Every Monday at 7pm for 12 weeks
    • OR with a set of dates - April 7, April 10, April 14, April 17
    • Review the Recurring Events data representation in the iCalendar specification for additional properties - http://www.ietf.org/rfc/rfc2445.txt
• CiviMail
  • Automated Recurring Mailings in civimail - for recurring meeting reminders etc.
    
    

Small Projects

• Dedupe improvements (prev/next support, caching)
• Flexible dedupe rules per profile / import
• Built-in support for event discounts
• Renew now links for memberships when created off-line (default contribution page per membership type)
  

Infrastructure issues

• Upgrade Smarty to v3.0
• Migrate to new DB layer? Doctrine or Drupal7's DBTNG
  

Some prior stuff which might be good make it happen projects

Core CiviCRM

• Modify form and page code to reduce the work done on ajax requests. For example, looking at Contribute_Form_Contribution - the call to load custom data does good job since it returns quickly in functions once it's work is done. However, the formType invoke (which loads credit card payment block and additional panes) isn't structured properly since the code does NOT return in preProcess and setDefaults even though no work is needed.
• Finalize HTML markup and css conventions for all forms and pages and implement modifications. (Layout Standards|confluence/display/CRM/Layout+Standards\)
• Add ability to create group categories and filter the category list based on those classifications. Also brainstorm other ways to improve navigability of groups as the current very basic structure becomes cumbersome when a large number of groups are created. Possibly add permissions so certain groups can be flagged as reserved by high level admins. (BPS)
• Cleanup "billing address" functionality. Currently we have two ways to mark billing address (is_billing flag and Billing location type). This is confusing and redundant. (KJ)
• Separate operations / permissions for "Move to Trash" vs. "Permanent Delete" for contact records. The default action is "Move to Trash". Users with "Permanent Delete" permission can periodically run an "Empty Trash" operation. While implementing, look at providing immediate Undo action for deletes and eliminating the extra clicks (are you sure...) - as described here: http://www.alistapart.com/articles/neveruseawarning/ (XD: high on my wish list)
• Enable multiple "used for" selections for custom groups and ability to duplicate custom group sets (http://forum.civicrm.org/index.php/topic,4213.msg18391.html)
• Introduce consistent date created, date last modified solution across the system (maybe together with moving logging to db layer?)
  

Usability Improvements

• Possibly the ability to have the session show OR hide all help text so user can switch from "beginner mode" to "advanced mode" when ready. (Let's look at other sites for examples of how this can be done. dgg)
• Allow custom fields to be edited/displayed within existing core fieldsets.
• Move to tab interface for CiviMail creation pages
• Make CiviMail report more user friendly. May be add graphs etc.
  

CiviMember and CiviContribute

• "Get Donation Button" feature - provide a screen under "Configure Online Contribution Page" where the user can input button title, and select some style properties (e.g. bgcolor, font...) and we return an HTML snippet that they can paste on any page or block to add a donation button. We can use the CSS-generated "button" code that we currently use for our action buttons (e.g. >> New Event )
• Offline recurring contributions (may overlap with pledges? see http://forum.civicrm.org/index.php/topic,2600.0/topicseen.html for additional thoughts)
• Mail-merge tokens for aggregate values (esp total contribution amount YTD, MTD, since inception)
  

CiviEvent