Agreed. At my job we've integrated all the tools. Developers have to put the ticket number in the commit manually, but then the tooling will attach the commit to the ticket automatically. There's also a bot that checks what you're committing and adds checklists for riskier things.

Then the ticket is picked up on merge to master which creates a change list. Everything gets deployed to QA where it's tested. QAs go over the changes and approve it, then developers push to production. Afterwards a random developer from a different team is picked to do a post-deploy review which spreads knowledge and sometimes picks up other changes.

If something can be automated it should be :)