You both make good points. The issue is that the fitness of your source of truth often depends on the direction of your perspective. If its from top of the organization down then the messy granularity of a single QA testers workflow status snapshot is too much detail. But on the ground where the rubber meets the road it is noisier and team communication requires that flexible approach to detail.

These guys solve the problem where Jira is either positioned facing up (clean) or facing down (messy details) and doing your own translation is usually a complex time consuming and error prone API effort in comparison to live spreadsheet data you can produce (down) or consume (up) any way you like. Similar workflows on Make/Integromat or Zapier also help re-orienting the use case direction if you are allowed to connect them.