docs: [#227] add issue number to refactor plan

Author: josecelano

docs/refactors/active-refactorings.md

@@ -1,5 +1,5 @@
 # Active Refactoring Plans
 
-| Document                                                                                              | Status      | Issue | Target                                            | Created      |
-| ----------------------------------------------------------------------------------------------------- | ----------- | ----- | ------------------------------------------------- | ------------ |
-| [Rename Test Functions to Follow Conventions](./plans/rename-test-functions-to-follow-conventions.md) | 📋 Planning | TBD   | All test functions with `test_` prefix (21 files) | Dec 12, 2025 |
+| Document                                                                                              | Status      | Issue                                                                  | Target                                            | Created      |
+| ----------------------------------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------------- | ------------------------------------------------- | ------------ |
+| [Rename Test Functions to Follow Conventions](./plans/rename-test-functions-to-follow-conventions.md) | 📋 Planning | [#227](https://github.com/torrust/torrust-tracker-deployer/issues/227) | All test functions with `test_` prefix (21 files) | Dec 12, 2025 |

docs/refactors/plans/rename-test-functions-to-follow-conventions.md

@@ -836,4 +836,5 @@ Remember to run `./scripts/pre-commit.sh` before each commit. This ensures:
 
 **Created**: December 12, 2025  
 **Last Updated**: December 12, 2025  
-**Status**: 📋 Planning
+**Status**: 📋 Planning  
+**Issue**: [#227](https://github.com/torrust/torrust-tracker-deployer/issues/227)