No, what he is describing is a well-rounded
staff level engineer. As you get more senior and take on more responsibilities, you start having to think about everyone's work and how it all fits together, you think about how the project fits into a product that meets the customer's need (unless you have a dedicated PM, which is becoming rare), you have to think about deadlines and how the project is tracking towards it, you have to think about other teams and how their work intersects and how their dependencies are timed to ship in time for yours, you need to communicate up the totem pole to actual managers. And, yes, you have to hold your nose and open up Jira.
I don't know where these "pure" perfectly spherical software engineers work who are super-senior staff level, but still do nothing but type in code. I've never seen them. As soon as you advance beyond the entry-level, you need to broaden your scope and be more of an actual engineer rather than just someone who writes code.
The manager's job is (among others) to make sure the team is working well together, solve any inter-personnel issues, work with each of their directs on career development, sometimes provide direction of what to work on, sometimes actually assign individual tasks, pass down announcements and direction from the higher-ups, help to manage the team members' performance, and work with HR when needed. They're not there to do all the stinky non-code-typing things in your project.