When deleting a queue the entire hierarchy of the storage account collapses

[ahawes-clarity]

Preflight Checklist

• I have installed the latest version of Storage Explorer.
• I have checked existing resources, including the troubleshooting guide and the release notes.
• I have searched for similar issues.

Storage Explorer Version

1.27.0

Regression From

No response

Architecture

i86

Storage Explorer Build Number

20221201.1

Platform

Windows

OS Version

Windows 11

Bug Description

First this Bug Report form does not provide an option to enter ia32 as the Architecture.

Whenever I delete a queue the entire storage account tree collapses. What I would expect is that only the queue I am deleting is removed from the tree and the tree remains expanded as it was.

This is particularly troublesome when I have multiple queues to delete as it requires me to re-expand the storage account for each queue I need to delete.

Steps to Reproduce

1. Launch Explorer
2. Expand a Storage Account
3. Expand the Queues node
4. Right-click on a Queue and select delete
5. The storage account immediately collapses

Actual Experience

Whenever I delete a queue the entire storage account tree collapses.

Expected Experience

What I would expect is that only the queue I am deleting is removed from the tree and the tree remains expanded as it was.

Additional Context

No response

[ahawes-clarity]

I forgot to mention that this behavior is not new and has existed as far back as I can remember. I am just now posting about it because I have the time. I guess I am very surprised that this issue has not been address yet. But maybe there is something else going on that I am not aware of.

[MRayermannMSFT]

@ahawes-clarity thanks for opening the issue. I tried to reproduce what you describe in both version 1.27 and 1.28. In neither version did I see the hierarchy collapse. Any chance you can use screen to gif (https://www.screentogif.com/) to record a reproduction of the bug? Perhaps there's a small/not-obviously-important detail we're missing in the reproduction steps.

[ahawes-clarity]

Recording attached. Maybe it is because I am in Quick Access? Yes, I think that might be it. I can't reproduce in the normal Queue listing. 

[ahawes-clarity]

@MRayermannMSFT, my initial reply by email did not include the attachment so I edited it manually to include it.

[MRayermannMSFT]

Perfect! The missing detail was that your nodes are under quick access. I'll look into this now. Thanks!

[MRayermannMSFT]

😊

[ahawes-clarity]

@MRayermannMSFT Does that mean you found the issue or that you can't reproduce?

[MRayermannMSFT]

@MRayermannMSFT Does that mean you found the issue or that you can't reproduce?

Apologies for the confusion. It means I've fixed the issue and we'll include the fix in our next release.