search

CrisisCleanup / crisiscleanup-1

[OLD] Legacy Crisis Cleanup on GAE/Python
https://sandy-disaster-recovery.appspot.com
Other
8 stars 4 forks source link

Each Work Order has Several Statuses, one per Phase? #139

Open aarontitus opened 11 years ago

aarontitus commented 11 years ago

Original author: v...@aarontitus.net (January 13, 2013 22:51:31)

Based upon the phases identified in #134, each work order should have a status for each phase, subject to the logic in #97 and #66.

For example, if the phases are "Clean-up," "Mold Remediation," and "Rebuilding," then each phase should include a dropdown for "Closed, completed" "Open, needs followup," etc...

Original issue: http://code.google.com/p/sandy-disaster-recovery/issues/detail?id=139

aarontitus commented 11 years ago

From v...@aarontitus.net on January 14, 2013 14:46:08 This means that a single work order could eventually be claimed by several organizations; one per phase.

aarontitus commented 11 years ago

From cpw...@gmail.com on February 05, 2013 17:55:57 I will take this and #134.

aarontitus commented 11 years ago

From cpw...@gmail.com on February 06, 2013 17:33:59 As part of this, I have been looking at how to support claims per phase (as per #1 above) - but it would be a major change affecting a large part of the codebase.

I recommend splitting it out to a new issue and handling after agreeing an implementation for basic phases.

aarontitus commented 11 years ago

From v...@aarontitus.net on February 07, 2013 15:28:41 I understand that this will affect a large section of the codebase... but the reality is that on any given work order, the organization doing clean-up will likely be different from the one doing mold remediation or rebuilding.

We could create a setting that automatically unclaimed the work order as soon as a phase was done, but this would eliminate a record of who did what, and it would be difficult to allocate volunteer hours appropriately.

aarontitus commented 11 years ago

From cpw...@gmail.com on February 07, 2013 17:04:26 Understood. I'm just recommending doing it in two stages to avoid a jumbo commit that would be harder to review.

aarontitus commented 11 years ago

I'd like to reconsider this one. For sake of simplicity and usability, there should be just one intelligent status-- the system knows what the organization does due to their profile; and clicking "closed" should automatically update each of the phases' statuses. This raises all kinds of new conditions, though... for example, OrgA's profile says they do muck-outs and mold remediation. They close 500 work orders. Later they change their profile to include Rebuilding. Should the 500 show back up on their map as unclaimed and ready for rebuilding as a result? I'd also like to discuss adding an "Ignore" status/button. This status would unclaim and hide the /- what would that do to phases and statuses?