It is necessary to store links between “Obligations under contracts” and “Functionality implemented in products”. Is there a ready solution?

Question

Project management

The organization develops information systems for the customer. Solutions are quite large. Projects develop in an evolutionary way, functionality is added mainly on the basis of individual technical requirements, which can be more than a dozen per year. In addition, in the course of implementation, we often deviate from the initial requirements, agree on additions, changes, and so on.
For a long time I want to acquire a tool (preferably a multi-user system so that it fills with data faster) in which one could:

• Create a list of Contracts (or Terms of Reference, Projects, Stages, Versions)
• Enter all essential requirements from these TORs and project documentation (Requirements Tree)
• Create a functional description of the product (Function Tree), as well as the content of the contextual HeLP and (or) documentation
• Describe the structure of the user interface (Form Tree)
• Store a list and short description of database tables (procedures, triggers....)
• Describe the connections between all these structures
• Provide search functionality

Usage scenarios are:

• When solving problems of technical support - to find a description of the initial statement of the problem and goals - "why it was done and why it was changed" by the implemented interface.
• When developing the system, making any changes, for example, in the interface, to know what obligations we have in terms of changeable forms, in terms of functionality, and which, for example, should never be abandoned.
• In the process of implementing the requirements of the new TOR, it is easy to collect changes made by programmers, for example, the composition of the changed forms of the system interface, in order to facilitate the setting of tasks for the documentation department.
• ....

Can anyone tell me if there is a ready-made solution that is close in functionality?

Answer 1

Confluence WIKI. We have it in addition to Atlassian JIRA.
In it, all requirements are conveniently linked by anchors to other documents where features are described. And it is desirable to make footnotes with the task number in Jira. Is it worth the question? Yes, it's worth it. Easier to control acceptance and development. Although separately on acceptance it is necessary to do PMI testing.
At the same time, WIKI beautifully knows how to notify about a change on the page. If something is major, then all participants in the mail receive a beautiful notification with the underlined text added. Very convenient, I must say.