Personally, I would prefer to have a more 'robust' way to keep track of things like that. By leaving comments like that, I think you run the risk of either forgetting about it, or losing the comment in some refactor or even having the TODO comment in a different part of the code, where it is not relevant.
Creating an issue on gitlab or github, or a card on trello, or whatever issue tracking system you may use in your team seems to be a better solution. A proper issue with a clear description of the problem to solve in the future will make everything clearer.
I'll go ahead and say no.
Personally, I would prefer to have a more 'robust' way to keep track of things like that. By leaving comments like that, I think you run the risk of either forgetting about it, or losing the comment in some refactor or even having the TODO comment in a different part of the code, where it is not relevant.
Creating an issue on gitlab or github, or a card on trello, or whatever issue tracking system you may use in your team seems to be a better solution. A proper issue with a clear description of the problem to solve in the future will make everything clearer.
How would you show what exactly has to be changed (refactored) in code in issue?
Code and line numbers could be changed with a time.
Here is for example one suggestion to parse TODOs and create tickets automatically
TODOs bot does (mostly) that suggestion, for free hehehe