Projects to consider

• Tim - add case id to hooks (post/pre mostly)
• more dynamic timeline - hook to prepopulate the next scheduled activity / (rules integration?)

• DGG - Check if org as client is working? Can do contact to contact relationship?

• Deepak - Support custom fields for Cases: CRM-8508

• Dave J - http://civicrm.org/blogs/lcdweb/case-improvement-ideas
  • filtering activity assignment by api get params (stored in option_value.grouping)
  • filtering case role assignment by group (maybe use settings.xml to set a default, then use case type xml to override. Maybe using grouping field in option_value to specify group id(s))
  • override case resources group at the case type level
  • (Lower priority) Roles show up as relationships on a contact's relationship tab, including roles where they are the case manager, making it too unwieldy (ran by Brian and Physician Health the simplest solution: remove case relationships from relationship tab - Update Brian doesn't necessarily want removed, just separated and a way (case id / subject) to see which case to tell them apart)

• Dave D Optimize dashboard query when choose all cases
  • Seems at least a couple orgs don't use the case dashboard recent/upcoming section, at least not the case managers themselves. Not just a speed issue.
  • case summary at top of dashboard is still useful
  • maybe make them into dashlets instead and use on main dashboard
  • feedback indicates most orgs need to see "my open cases" and it is useful to see upcoming activities (current dashboard only includes ones with scheduled activities)
  • at least one org wants to keep the dashboard, although routinely customizes it

• Search # + ID to go to record by ID (contact, case, contribution ....)
  • kurund/xavier investigate doing this as part of re-implementation of quick search box

• Dave D - Add new contact on the fly when creating relationship (more generally even in any location)

• Yashoda - when enable civi component, if no existing config defined, have sample config "work" without requiring more steps
  • Merge the sql to xml, and then have system figure out what needs to be put in option_value.

• Use contact search and create new case
• Use find cases and then close multiple at once (generalize to change case status)
• revisit reference_activity tag and what it's relative to (Xavier) (maybe covered by dynamic timeline above)

• Email Processor changes (from Andrew Clarke / Physician Health Program)
  • allow me to select multiple activities at once to be filed on a case (perhaps with a checkbox interface similar to what appears in a contact search);
  • allow me to delete activities that have been attached automatically to a contact, sometimes by mistake;
  • allow me to see a reference in a user's activity stream after an activity has been filed on a case: something like "activity filed on case 25098"; (is problem that don't know if already filed?)
  • allow me to configure an organization contact with an email domain, so that all emails from that domain are filed on that organization's contact, rather than on individual contact records. There are some organizations with which we have very loose associations, and we don't want to bother maintaining individual contacts - we just want to see all of the email from that organization in a single stream.

• max_instances at the case type level to limit number of cases (can this be done by the validate hook for open or the open case post hook or the case creation hook)