Ideas / Wishlist for v2.3 release

• move all dojo to jQuery
• rearrange contact edit form / rethink contact view

• some event improvements
  • update participant info
  • waitlist
  • email address not required
  • tweak additional participants flow
  • cancel registration
  • add/remove more people
  • badge printing
  • expire pending pay later
  • integrate google calendar
  • attendance list
  • confirmation number for event registration

• miscellaneous useful stuff
  • html emails
  • integrating drupal "action/triggers"
  • delete permission
  • smart group display for contacts

• civiauction (lobo)

• consulting work

• Import
  1. Notify the required field using different colors during the mapping.
  2. Use Default value given by user when data is absent of that row/column.

• CMS
  follow the CMS users setting
  like in joomla Allow User Registration is disabled then civicrm should follow this during the online contribution/registration with profile configure to allow CMS user create. same for Drupal

• Chart
  Differentiates the contribution using (using pChart )stacked bars. ( Event/PCP/Membership ) etc

• Ajax driven delete for "Delete" location. Rather than redirecting to another page it will show dialog on same page and update page if deleted.

•  Implement Contact image feaure, people should be able to upload contact image rather than adding custom data. We can also show that image in Contact Summary etc.

• Implement graphical report for CiviMail report.

• Implement ajax driven drag-drop profile builder, as discussed on http://forum.civicrm.org/index.php/topic,4627.msg20180.html#msg20180

• CiviMail
  For inserting token in mail body instead of using multi-select w/ javascript, can give user interface like Checklist w/ proper name (for Ex. we can use ForwardMailing instead of action.forward ) which are not directly visible in mail body but will be send with body.

• Proper error handling instead of fatal errors. May be user friendtly error codes. Also should we give fatal errors to font-end users? Like when payment processor is not configures for contribution page etc. we  give fatal error. (Or we should assume that admin will fix fatal errors, before site goes live.)

Components

• CRM-3583 Make "Administer CiviCRM" section component specific and pluggable
• CRM-3584 Clean up setContext() functions use in Tab.php component classes
• CRM-3955 Make activity types management (component assigning) more consistent and less CiviCase specific
• make Touchstone component fully working and a base for walk-through demonstration on creating CiviCRM components
• design and implement integration layer for CiviContribute/payments (on occasion of CiviAuction), later on CiviEvent and CiviMember could be fitted with the solution
• design and introduce new solution for consistent logging accross the system
• move component related XML schema definitions to respective component directories (will help in further isolation of components from the core)
• abstract/introduce simple email notification framework, that would allow sending template based emails to administrators/users about new events/pending tasks/etc (for example, letting administrator know about new PCPs for approval)
• Introduce per-user preferences infrastructure