Out of curiosity, what triggered this change?  Did we encounter a scenario that requires the view name to be unique?

From the UI point of view, I can see this being useful based on how the views are currently listed on the Changesets page; however, I am curious the motivation.

An alternative to uniqueness by org might be uniqueness by definition, since the view also belongs to a definition.  Today, we have a similar relationship/behavior for product & repo, where repo name must be unique per product.