Case status Closed is hard-coded, consider allowing multiple closed states

[davej]

Hi,

Use case:
Case = application where multiple end states are possible, e.g. rejected at stage 1 or 2, accepted.

Discussed with Lobo on IRC:

<davej_> case_status: I see that state 'Closed' is handled specially in code (CRM_Case_BAO_Case::getCases) - would be nice if there could be multiple 'Closed' states, e.g. Application Granted/Refused.
<dlobo> good suggestion
<dlobo> wanna post on the forum
<davej_> dlobo: will do.
<dlobo> we should generalize that and allow multiple statuses to have the "closed" property
<dlobo> we can potentially do that in 3.2
<davej_> All the out-of-the-box case_status & encounter_medium options have reserved = 1, so I'm wary of meddling with them but need a different set of options.
<davej_> No UI for these 2 option groups at the mo, but I can live without that.
<dlobo> i think there is a generic UI for all option groups
<dlobo> just no links have been exposed...
<dlobo> so something like: http://trunk/civicrm/admin/options/activity_type?group=case_status&reset=1
<dlobo> fix the url for your situation
<davej_> Ah, great, that works. I manually disabled Closed in db & got SQL error in getCases due to no closedId. UI sensibly disallows disabling reserved options.

Case status 'Closed' and 'Urgent' are hard-coded by name in CRM_Case_BAO_Case::getCases.

Case status 'Ongoing' is hard-coded by id (1) in CRM_Case_Form_Activity::setDefaultValues, rather than looking up by is_default.

Dave J

[lcdweb]

+1 to allowing additional case closed options

[FatherShawn]

This would really enhance a project that I'm working on.

[Donald Lobo]

Would be great for someone to step up and help sponsor / contribute code to make this happen

lobo

[FatherShawn]

Extending this feature would logically involve fixing this possible bug.  I'm willing to have a crack at it.  Feels small enough to possible and involved enough to push me a bit.