Code, UI and Usability Sprint Plan - London August 2011

Adding various topics from the forum thread split by how much work is involved:

Quick fix Projects (< 1 day)

• move the quick search backend to the api - Xavier / Kurund
• add context to hook_civicrm_tokens and hook_civicrm_tokenValues - Lobo
• More friendly 'add to calendar' for event pages (see http://lanyrd.com/2011/civicon/) lcdweb
• Tweet and Like added for event, online contrib and pcp pages lcdweb
• move the register now to the top of the info page for events xavier
• put a link/some links (for admins) in the info page for events xavier
• possible modifications to 'more' action links on selector rows (single mouse-over pulldown for all available actions?) xavier/kyle
• instead of just one title, have both a title and a label for the profiles (so you can have something readable in the back office and user friendly in the front office xavier (note that profiles already have a name field in the DB)
• On tabbed interfaces (event config, contrib page, mail) I would like to see the addition of "Save and Next". The current behavior requires two clicks when the user wants to navigate through the multi-step process in a wizard-type way. The tabs are an improvement when editing and skipping steps, but we lost the process nature of a wizard which is most useful when first creating the record. lcdweb
• Set focus to first field in all forms when they load (jQuery) dgg
• Add "add to group" and "pdf letter" actions for component searches dgg
• event settings and other forms w/ From and TO fields: set TO = FROM when FROM is selected if FROM is empty dgg
• update 'create relationship' form to use contact autocomplete and allow creation of new contact via pop-up profile dgg
• implement new billing mode 'POST to external' for payment processors (where we need to save data in Civi & then present a form that POSTS to the external site) Eileen
• finalize latest civicrm_engage xml file jamie
• civicrm_engage survey report displays respondents ordered by street number, on-screen display should use the same order jamie

Involved but doable (1-3 days)

• Drag and drop UI for Profiles (add and move fields around, etc.) kurund
• relative dates for search forms (advanced esp since can be used for smart groups) dgg / lobo
• modifying one existing ajax interface to use the api as the backend: http://issues.civicrm.org/jira/browse/CRM-7970 - Xavier
• Add grid editing (as more powerful batch editing or for the simple list admin) jqGrid - Xavier / Kurund
• add more in place editing (jeditable or simplier ones, eg changing status, adding a phone...). Remember that all edits have to be via POST and qfKey'ed - Xavier / DGG
• Optimize CiviContribute Queries - Eileen / Lobo
• Web-editable templates, esp. profile templates – I would like to enable implementors with basic HTML skills to tweak the layout of forms (esp. profile forms). This can currently be done by writing a new .tpl and dropping it in the right directory, but it presents more issues with training, maintainability, user-management, etc. In my mind, a good solution would: Tim
  • Include an "Edit" link for each profile form; this would be populated by some default "tpl" code which imitates the main file
  • Include a validation tool which probes user-supplied .tpl files to identify missing/invalid form elements
  • Be consistent with the file-naming conventions in "civicrm/templates" and "custom templates".
  • Be optional - so that admins can disable it if it's required for their security posture
• Eliminate extraneous confirm dialogs (especially on reversible actions like move to trash and disable) - http://forum.civicrm.org/index.php/topic,21024.0.html xavier
• I'd like to see the button formats reviewed – see http://www.lukew.com/resources/articles/PSactions.asp. Specifically, we should consider visually distinguishing the cancel buttons (personally I like the text-only example). Also, we have some old formatting still in place which uses non-breaking spaces to separate buttons. that should not be necessary now that the css class designations are in much better shape. lcdweb
• Efficient multi-tenant background processing Tim
• Reorganizing CiviMail workflow in 3 steps: Create Mailing, Choose recipients, Preview and Send ( Test email ) dgg / kurund
• Auto update membership end date for membership payments jamie
• Refactor command line scripts to consistently: use cli.php and (hopefully?) remove need for user/pass/key when running from the cli and add drush commands for more cli scripts jamie
• Automate the configuration and xml import for civicrm_engage so it happens automatically when the module is installed

Long term restructuring / Prototypes

• Integrate and start code migration towards DBTNG Tim / Lobo / Deepak
• Use Drupal6 as a distinct UF for 4.1. Figure out how to handle drupal/modules dichotomy. Form community team to manage and support this UF Tim
• add params to token/integration CiviMail/Civient http://civicrm.org/blogs/xavier/ideal-workflow-your-events-registrations Lobo/Xavier
• Admin menu that is organised Xavier/DGG