|
Copper has been amazing as a project management tool. However, one issue we are having relates to individual resources posting issues with tasks and how those issues are dealt with. The problem is compounded by the shear mass of email communications that copper generates for our 15-person, 25 project team and the fact that issues tend to get buried within a long list of comments.
We would love to see issues separated from comments and issues become a child of tasks. When an issue is flagged, it can be assigned to a resource (which would show up on that resource's springboard) commented on and later marked resolved.
Further, project managers can view the issues for a task, view the issues for a project (all task issues organized by task) and view all of the issues for a client (for all projects and all tasks.)
I realize this may be off-purpose for Copper, but it would allow Copper to become a better communications tool in facilitating completing projects in addition to project scheduling. |
|
