Hey guys, I'm new to a dev management role. One of my responsibilities is to write tasks and do code reviews for the team. I keep getting issues in code due to the lack of contextual understanding of the codebase. How much detail should I include in a task? Should I expect my team to understand the context of the task/codebase?

Add context to your tickets but don't get down to the nitty gritty details unless you actually have too, devs should be able to think for themselves unless you manage a sweat shop?

Your devs should know the codebase well enough to implement changes to it, unless it's a 3rd parties code base, but even then it doesn't take all that much to map out what's going on already and implement changes needed.

Maybe @AleCx04 has some pointers.

what @C0D4 said is pretty legit. Overall you are expected to not get lost or to understand the code you are looking at, but not memorize all of it! take some time to get acquainted with everything you see and the main devs behind that codebase. If you are supposed to be better (as in, not just a project manager) then coach them for certain things.

Take it one day at the time. And yes, they are developers, they are expected to be able to complete the task, to understand it and keep them on track is your job tho.

thank you @C0D4 and @AleCx04 for the advice, I'll keep that in mind.