Just opened a giant #refactoring ticket for an entire service that's kind of a rats' nest of public methods calling other public methods, database access in unexpected places, and low test coverage. I'm pretty pleased with being in a position to do that.

However, the problem is that this ticket is HUGE in terms of effort. How do you approach splitting up a ticket that's about refactoring and writing unit tests for a 5,000 line service class into controller, service, repository, and utility layers where you don't even know ahead of time what piece of code depends on what?