Dialogues Shouldn't be Required for "Current" Projects that Get Pushed Back to "Queued"/"Back Burner"/etc.
Sometimes active department projects are halted due to unforeseen obstacles, new priorities, etc. When this happens, department Dashboards get hit because project dialogues stop.
There should be a way to prevent this from happening. Maybe more date fields to track when the "current" status changes, which the Dashboard would read. Or maybe tying the project status to the Dashboard so it only looks for dialogues for "current" projects? (I know statuses can be edited, but maybe there is a settings option to declare which project status represents "active" so the Dashboard only looks for dialogues from that status)
I'm not sure if other users delete the "actual start date" of the project to prevent this from happening...?
Please sign in to leave a comment.
Comments
1 comment