Project Trackr Development Log Building a better web based project management solution

The title of this post may be a bit misleading, especially as I’ve said in the past that communication is a key part of project management. The thing is, that was before I thought to add tickets, which has the same functionality as the messaging section and more, so really, there is no point in replicating the same functionality across 2 sections, as then some of the communication ould take place via messages and some via tickets.

As a result, I’m removing the messages section although this may cause cofusion with users unfamiliar with the term “tickets” so I may leave the messages tab in explaining the decision to leave it out, or just point to the tickets section.

The relevant table is shown below:

+----+------------+---------+------------+-----------------+----------------------+
| id | account_id | user_id | project_id | title           | SUBSTR(body, 1, 20)  |
+----+------------+---------+------------+-----------------+----------------------+
|  1 |          1 |       1 |          1 | Damians message | Should only be visib |
|  2 |          2 |       2 |          2 | Roms message    | Should only be visib |
|  3 |          1 |       1 |          3 | Branding Info   | A message in a share |
+----+------------+---------+------------+-----------------+----------------------+

The first message should be visible to the first user, the second message to the second, and then thrid to both. This works fine when viewing just a single project which is a leaf node in the hierachical representation of the project structure, but if viewing a project with one or more sub projects, the message from the sub project should also be displayed.

Read the rest of this entry »