Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MR-QA - Wrong deletion of a folder instead of the subfolder #3951

Closed
1 task done
kazoompa opened this issue Oct 18, 2024 · 0 comments · Fixed by #3968
Closed
1 task done

MR-QA - Wrong deletion of a folder instead of the subfolder #3951

kazoompa opened this issue Oct 18, 2024 · 0 comments · Fixed by #3968
Assignees
Labels

Comments

@kazoompa
Copy link
Member

kazoompa commented Oct 18, 2024

This issue is unique

  • I have used the search tool and did not find an issue describing my bug.

Version information

5.0.0

Expected behavior

Only the subfolder should be deleted.

Actual behavior

Several things: when user cancels the deletion confirmation SubQA001 selection gets cleared. Next, the hovering delete button next to SubQA001 deletes the parent.

Internal selection data discrepancy, the parent seems to be still selected.

We should clear selections when user cancels the confirmation preventing selection discrepancies.

Reproduction steps

  • Go to the Files/users section
  • Create a subfolder QA001
  • Go inside QA001 and create a subfolder SubQA001 within QA001
  • Select SubQA001
  • Click on the Delete button next to QA001 (parent)
  • Cancel the deletion popup
  • Click on the delete button next to SubQA001

Operating System (OS)

No response

Browser

No response

Contact info

No response

@kazoompa kazoompa added the bug label Oct 18, 2024
@kazoompa kazoompa changed the title MR-QA - Wrong deletion of the a folder instead of the subfolder MR-QA - Wrong deletion of a folder instead of the subfolder Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants