zappfyllc
commented
4 years ago @amenity thoughts on moving this to the icebox? We have project notes to capture ongoing information related to the project at a given moment in time, but this was moreso related to the idea of a channel-like method of communicating between project members. I don't think this is MVP and it's up-in-the-air on whether it's necessary at all, but I do think it's an interesting enough idea to explore so not sure about closing it.
amenity
Context: there are several feature requirements for the mobility project editor related to communication, including simple project notes (e.g. rich text field, user id, timestamp, etc.), correspondence (i.e. back-and-forth between project team members during specific phases of the project), and review requests (e.g. a project manager may assign a user or group of users to complete a review of the project in some manner). In addition to these requirements, we would be interested to know if there was a way to create Slack-specific channels for rolling communication within a project, but as Teams is being adopted across the city due to the enterprise licensing, it may be worth investigating if there's an easy way to integrate Teams in a useful manner for project-specific chat/messaging.
Questions
Identify potential lightweight technical solutions for the project notes, correspondence, and review request requirements. These could be React-complementary solutions or from a technology-agnostic service/product.
Research a Teams integration that could be effective in sending users from the Mobility Project Editor to a project-specific area of Teams so that requirements can be achieved via Teams rather than Mobility Project Editor (aka MoPeD would simply be the "in-between" tracker but not necessarily offering the robust functionality).
Identify requirements related to alerts/notifications that would arise from the above requirements (Amenity/JD).