Support Forum

[victor]

Hello,

In another post I commented about a need that I have: a system message when the tasks are created.

Thinking about it I found that this could be a powerful improvement if we generalize it.

I propose that TS has a set of system messages to reflect in the task history messages some system events that affect to the task by definition:

- Task_Creation : This system message would be sent automatically when the task is created. The message submitter is the task submitter and the message handler is the initial handler.

- Task_Description_Modified : The description was modified. The message submitter is the user that modified it.

- Task_Priority_Modified : The priority was modified. The message submitter is the user that modified it. In message description say from what old level to what new level.

- Task_Category_Modified : The category was modified. The message submitter is the user that modified it. In message description say from what old category to what new category.

- Task_Moved : The task was moved (parent changed). The message sumitter is the user that moved it. The message description say from what parent task (id) to what parent task (id) the task is moved.

- Task_File_Upload : One file was uploaded to the task. The message submitter is the user that upload the file. The message description say what file was uploaded.

- Task_File_Deleted : One file was deleted to the task. The message submiter is the user that deleted the file. The message description say what file was deleted.

Maybe there is more system-messages. I think that this is an usefull and not very hard to implement thing.

Thanks,

[admin]

Hello,

In another post I commented about a need that I have: a system message when the tasks are created.

Thinking about it I found that this could be a powerful improvement if we generalize it.

I propose that TS has a set of system messages to reflect in the task history messages some system events that affect to the task by definition:

- Task_Creation : This system message would be sent automatically when the task is created. The message submitter is the task submitter and the message handler is the initial handler.

- Task_Description_Modified : The description was modified. The message submitter is the user that modified it.

- Task_Priority_Modified : The priority was modified. The message submitter is the user that modified it. In message description say from what old level to what new level.

- Task_Category_Modified : The category was modified. The message submitter is the user that modified it. In message description say from what old category to what new category.

- Task_Moved : The task was moved (parent changed). The message sumitter is the user that moved it. The message description say from what parent task (id) to what parent task (id) the task is moved.

- Task_File_Upload : One file was uploaded to the task. The message submitter is the user that upload the file. The message description say what file was uploaded.

- Task_File_Deleted : One file was deleted to the task. The message submiter is the user that deleted the file. The message description say what file was deleted.

Maybe there is more system-messages. I think that this is an usefull and not very hard to implement thing.

Thanks,

Yes, seems very good idea. I now see one problem - those messages should link to some workflow (otherwise we can't search/etc), so we can
- implement it for all workflows (not so good idea, many problems when list of system messages changed)
- implement true workflow inheritance and inherit such message types from some system workflow (sounds great, but I how no ideas how to implement it yet).

[victor]

Yes, seems very good idea. I now see one problem - those messages should link to some workflow (otherwise we can't search/etc).

I think that would be a better solution do that this messages was link to a 'false' workflow (or not linked to none workflow).

This messages would be added to every message list with the others workflow messages. This is a wired work, by code.

The idea was define 'system-general-messages' this messages dont change status and dont change handler by that they have not linked to none workflow. This messages are managed by the system, by code.