Planning: To Do list - Githubissues

Your Comment - Company - To Do - explanation of what this menu is for The To Do list is a list where the users are reminded that certain processes are pending. For example:

when a new user 'purchases' a license in the webshop and fills out a model 210 tax form. It will show that we need to verify the data introduced by the client and present it manually.
when a user asks a question on accounting, we see in this list that we need to answer this request.
when a user has a technical issue or trouble, we need to help this user
When the manual or the guide need editing, we need to receive a suggestion on this list
A chat that has been sent by a user that needs answering The To Do list is therefor created automatically by the input from the users (sales, queries, bugs). It has to parts:
Todo things on content --> this will be assigned to the company workers
Todo things on bugs --> this will be assigned to the software programmers (superuser) To assign a 'to do' item can be a choice made by the user, but if they choose wrong, the person receiving the assignment must be able to revert to a different person. For example, if a tax worker from company A receives a technical query from a client, that is a bug, they must be revert to the superuser for a solution. Now it is programmed as a 'manual' system where the users have to manually add items. The idea is for it to be created automatically by all user actions in the system.

Reply - We think this is a new change in requirement . Please confirm weather this is the full requirement of TO-Do . So that we can start changes.

Note: This feature you will find in the first source code. The TO DO list is an integral part of the whole idea, it is to be able to keep track of the processes that need manual intervention in the software. This is not new. It is how the Company can keep track of it's clients and prioritise certain assignments

nirajconverthink / CIBERCONSULTORES

Planning: To Do list #34