How to properly fix technical debt?

Question

Project management

How to fix technical debt on a project? Now it's just a file with comments, but it seems logical to me to mark it right in the code in toDo.
What are the pros and cons? Or maybe there are some cases.

Answer 1

only with tickets, in Jira or something else in which technical debt is
maintained - a relative concept, something like a feature method
is either done or not / either works or no
further, you can hang depths on it (new ticket), or urgently fix bugs causing losses ( it’s clear that you can’t put them in a notebook or a ticket for storage; although on a fix, of course, a separate ticket)
and then - check / donkey and nasreddin himself - it may turn out that that depth is not needed, or needed, but not that,
or not depth at all, but simplification

Answer 2

There are many both paid and free task management systems, fix them in them. Starting from an Excel file (if there are few tasks), Jira (the most common solution) and hundreds of others. You can, for example, pile on HTML-PHP-MySQL, purely according to your requirements. Fixing todo in the code is not a good practice, as it does not allow you to structure tasks in any way, determine priorities, etc.

Answer 3

On paper or in the EDI system as a reasoned refusal in response to an interim acceptance certificate. With a listing of all items. Next point-by-point bargaining. Part of the debt will be recognized and repaid, part not. But at least something.