How to manage work plans and logs

My colleague sent a letter to discuss how to record work logs. We were very enthusiastic about the discussion, and we found that everyone was also quite different.
Here I will list my work in three types:
1. Plan
This is managed using the project. The advantage is that a master plan can be easily divided into multiple sub-plans and managed.
But for all the plans, I keep recording only one status. The reason for the unfinished activities in the original plan is not recorded, and the time and reason for the delayed completion are not recorded.
Later, according to my colleague's prompt, I found that I still need to record the changed state.
Some colleagues use Excel for management, but the calendar view provided by the project is lost.

2. Thoughts and questions
Record some ideas that cannot be implemented for the moment in the work and the problems that are unclear.
Currently, mybase is used for management, and its tree node management is what I need.

3. Detailed records
For specific outputs of an activity.
Because it is enterprise development, it is often called with the database to record the SQL statements used.
And documents to be provided to colleagues in other departments (Database Structure Change Request Form, etc ).
Information about the test cases for system integration testing (not in testcase or version control ).
This information is stored in Excel, Word, or TXT files (some are company-specific and some are free to choose) and managed through a certain folder structure.

4. MEETING
It seems that you have no choice but outlook.

It is not convenient for separate management of 2 and 3. The ideal tool should have tree-like node management capabilities like mybase, but also provide the ability to freely add node types.
Instead of the current, all nodes are text. For example, to add a PDF file node, the node is defined by the system by default.ProgramOpen.