search

DARIAEngineering / dcaf_case_management

Rails-based case management system for abortion funds
MIT License
87 stars 245 forks source link

List a line's appointments in next few days on the main call list dashboard #679

Closed colinxfleming closed 5 years ago

colinxfleming commented 8 years ago

Stems from #593

vtmeghan commented 8 years ago

@lwaldsc and I discussed - we don't think they should automatically be marked as urgent, but if there was a way to flag them in another way that would be great. Either by a section on the homescreen for "Appointments tomorrow" or "Appointments within 36 hours" that auto-populates, or by allowing searches by appointment date, that would be useful. probably need to complete #671 before this is possible/useful. @colinxfleming @NerdyGirl537 @mebates

mebates commented 8 years ago

I would suggest leaving this in the backlog and focusing on our Release 2 priorities.

colinxfleming commented 8 years ago

Agree with @mebates that popping into the backlog is the way to go here, now that we have some client feedback and we know that this isn't an urgent fix. Let's revisit in 2017.

lwaldsc commented 8 years ago

Oh definitely. This doesn't need to be a priority, but wanted to give feedback as we were going through questions.

On Thu, Oct 20, 2016 at 8:36 PM, Mollie Bates notifications@github.com wrote:

I would suggest leaving this in the backlog and focusing on our Release 2 priorities.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/colinxfleming/dcaf_case_management/issues/679#issuecomment-255264811, or mute the thread https://github.com/notifications/unsubscribe-auth/AKFqsM-Fo_wChcjiBVhLpnT9vn3QyosFks5q2AkDgaJpZM4Kaj3d .

colinxfleming commented 6 years ago

Swapping this to future features since it needs more context and some sense of how useful it would be.

colinxfleming commented 5 years ago

This is coming up on three years without any forward action, which makes me think there isn't a critical pain point around this. @alisonnjones @vtmeghan @deesriv @mlindberg61 can we close?

deesriv commented 5 years ago

This is one of the proposed interventions to prevent drop off, it doesn’t impact CM operations but it will reduce burden for callers— @alisonnjones and harum and I started having scattered convos about it but would love to revisit about what’s possible and reasonable!

On Sun, Apr 21, 2019 at 11:46 AM Colin notifications@github.com wrote:

This is coming up on three years without any forward action, which makes me think there isn't a critical pain point around this. @alisonnjones https://github.com/alisonnjones @vtmeghan https://github.com/vtmeghan @deesriv https://github.com/deesriv @mlindberg61 https://github.com/mlindberg61 can we close?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DCAFEngineering/dcaf_case_management/issues/679#issuecomment-485261791, or mute the thread https://github.com/notifications/unsubscribe-auth/AHHGGSCDFIRO2CLB2OHXXYTPRSD5TANCNFSM4CTKHXOQ .

colinxfleming commented 5 years ago

My opinion is that if there is a specific and identified pain point for CMs that this would address then we should keep it on the backlog and prioritize it accordingly. If it's not, then we should close this out as something we won't do unless it comes up again organically, since that probably means it's going to hang out on the backlog forever.

deesriv commented 5 years ago

For sure! Closing for now makes sense, but I don’t want to completely lose this thread, as it relates to some of the operational changes to CMing that we’ve been thinking about over the last few months with our strategic planning workgroups and such. Cool if we bring it back to y’all once we’ve ironed out a more comprehensive plan to handling/preventing caller drop off?

On Mon, Apr 22, 2019 at 9:16 PM Colin notifications@github.com wrote:

My opinion is that if there is a specific and identified pain point for CMs that this would address then we should keep it on the backlog and prioritize it accordingly. If it's not, then we should close this out as something we won't do unless it comes up again organically, since that probably means it's going to hang out on the backlog forever.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DCAFEngineering/dcaf_case_management/issues/679#issuecomment-485606113, or mute the thread https://github.com/notifications/unsubscribe-auth/AHHGGSD2NX6KQIFQHED4CJLPRZPPVANCNFSM4CTKHXOQ .

colinxfleming commented 5 years ago

yeah, if it comes back up organically as part of a broader thing then that's cool, but absent a broader thing we'll never get to it so there's no point considering it 'outstanding work to do'. thanks much @deesriv