Are there methods (and which ones?) of maintaining a task tree in the task tracker, in order to accumulate knowledge about the project?

Question

Project management

There can be thousands of tasks in the tracker, and finding the right one without knowing the name becomes problematic.
One of the goals pursued is to have a list of "root tasks", delving into which it would be convenient to find specific tasks.
For example, the project is an online store. One big task “Payment Methods” can be singled out, which will exist, in fact, forever. And within the framework of subtasks, solve problems on the topic.

Answer 1

Marking the task with tags with subsequent filtering will be more efficient. Asana can add tags to tasks.

Answer 2

And here I will tell you a strange thing. You seem to be using the issue tracker for other purposes. You store documentation there, and then look for it. Do not do it this way. I'm sick myself. Zhira was big and fat, with that confluence a mess and some worthwhile information. You need to force yourself to keep documentation, requirements and conclusions in the place intended for this, and track tasks in your own. In this case, the task history is needed only for retrospectives and statistical analysis.