I've found the lesser of two evils to be that Product integrate as closely as possible with engineering, which means using either Jira or GitHub issues for high"er" level deliverables. You have to be careful not to use too much of the textbook PM speak--"As a <user>, I can do <new novel stuff> with the platform"--but if you orient yourself around the logical scoping of engineering work, it's a whole hell of a lot easier for engineers to tie their own work items into the progress (or unfortunate lack thereof) that all of us are inevitably expected to report up to our various business leaders.
That does require some technical acumen. I'm the first to admit that I don't have any of the formal bona fides for said acumen (and I deal with a great deal of imposter syndrome as a result). But when I listen to the engineers, understand their technical blockers, AND colocate our work items, I usually have an easier time.
And yeah, I still gotta copy/paste a bunch of shit into Sheets/Slides for management