This makes so much sense! I had done a deep-dive on brand from a data standpoint, including cyclical factors, and there's a huge amount of leverage here. Brand is typically the largest intangible item on the balance sheet, but quantifying that value is hand-wavy at best. Are you taking a structured, consistent approach to this across businesses?
I've got a couple similarly-sized hunks of aluminum and vanadium that I got from a steel mill tour when in college. I enjoy the difference in densities in my hand, but I don't know about $130 of enjoyment for one more in the set.
indeed, that's where we ended-up, by using Linear which provides the layer of abstraction. it's just disappointing because it's a long-standing issue, and relatively easy to solve (based on the fact many 3rd parties have).
What if I want to define a new feature that has both backend and frontend tasks, and have separate repos for the FE and BE? Which repo do we create the issue in?
It floors me that they haven't addressed the underlying architecture issues that made Issues unusable: Issues are only for a single repo. Business users don't (and shouldn't) know what repo to add an Issue to. This is why we moved away from Issues and none of these new visualizations make the product usable until they deliver multi-repo issues.
I toured the "Corner House", the Cheka headquarters in Riga a couple weeks ago. After seeing the prison and execution room, it was really moving to hear about the Baltic Way. It was a powerful symbol to the powers of oppression, and incredibly brave.