Interesting how perspectives differ. Having used Jira for many years, I think it's straightforward for engineering work, but particularly hard for PMs and mana

Interesting how perspectives differ. Having used Jira for many years, I think it's straightforward for engineering work, but particularly hard for PMs and managers. Why? On the engineering side, it's pretty straightforward to integrate into a lifecycle. But for PMs and management it's a nightmare because they still haven't gotten their birds-eye-view roadmapping / bulk editing act together. The usual issue I have with Jira is that the engineering team gets it integrated into their workflows, things work ok, but it's a continual challenge getting global rollup views to the business at large. We keep ending up with Excel, Airtable, or what-have-you high level views that then point to particular Jira issues for details (yes, we've used Portfolio). I think this actually might be a fundamental issue that is masquerading as design issues on Jira's side, because when you're doing roadmapping views you want to continually refactor them to reflect better metaphors and realities, whereas when you're doing issue tracking you want issues to stick around and be solid entities linked intimately into the history of the software application. So tools like Portfolio have to juggle both ends.