Closed DanielleCogs closed 8 months ago
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
Describe the Bug with repro steps
Users can remove parent objects from the map and this can make the hierarchy confusing. We should have a broader conversation about how much control we give to users over items on the map, and how we can make hierarchy more obvious. (bonus: look into how we choose to load schema nodes from saved state)
in the below example: there is an object that is the direct parent of NAD01 but it is not visible on the map
Screenshots or Videos
No response
Version
2.81.2
Additional context
No response
AB#25754083