We use dedicated Discourse topics, some tags and some conventions to track the status and progress of the Edgeryders’ companies projects (company-internal documentation here). This topic is to discuss what extensions to that basic journal feature are needed, if any.
Initial collection of ideas I have in mind for that already:
Automating comment for status and field changes: A custom plugin could post these comments whenever a user updates the
status-*tag or a field in the first post. The comment thread would then closely resemble how it looked in the Drupal version. It can be implemented with inspirations from the Discourse core “discoursebot” user. In addition, it would allow us to switch to a unified mode of updating a journal: simply edit fields in its first post, which would be a wiki. No strikethrough, no
status-*tag editing etc… The bot would post a comment about the change and who made it, and also adapt the
status-*tag on its own. Potentially, BBCode tags like
[status]…[/status]would be introduced in the topic template to simplify this task for the software.
Tag for reuse candidates: To mark projects that are esp. promising for reusing / recycling them, we might want to introduce a separate tag that would be assigned in addition to “
project-dropped”. Such as “
Tag for crisis mode: As a simpler replacement for the former “Attention needs” field in the Drupal version, we might introduce a tag
journaltag-crisismode. Or something less strong to indicate projects that need special attention to be successful. Can be further emphasized with an icon in front of the title, like one of . (The usual named codes like
:fire:also work in the title.)
Bringing back the “Attention needs” field: Maybe simply not needed, as there is a strong correlation with “project state”. In the Drupal based system, it encoded the level of care with which the project must currently be handled. If you are waiting for the client to react to a proposal it might be low (“awareness”); if the client is waiting for you to make a proposal, or if the project is active, it might be higher (“management: attentive”). In general, “awareness” denotes a passive state, “management” an active one.
Profect lifeline diagram: Add a diagram to a pinned topic in category “Project Journals”, or to a custom admin backend page, that shows the lifeline of every project as it changes its status over time. Status changes would be tracked from post revisions. Embedding the diagram into a Discourse topic is somewhat complicated but possible via a third-party diagramming web platform and custom OneBox embeddings – see this discussion.
Tag for project manager: By assigning tags like
manager-matthiasand changing them depending on who is project manager, we would (1) provide everyone the option to have an overview of the projects they are managing by visiting the corresponding tag page, (2) unify how field values are changed: by tag, not by editing a wiki. The wiki would only contain things that don’t change (client, client contact info).