You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should reporting bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
Per discussion in feature request 3914 if you could please ensure that container=0 is set for all Zone shapes and verify that shapes placed inside the Zone do not move when the Zone shape is moved. Thanks!
This applies to all Zone shapes:
Access Group
Account Group
Resource Group
Security Group
Instance Group
Placement Group
Availability Zone
Generic Zone
Based on release 24.8.6:
Please ensure that container=0 is set for all Zone shapes.
Verify that shapes placed inside of each Zone do not move when the Zone shape is moved.
Initial testing after manually changing a Zone shape to container=0 now exhibits the expected behavior (shapes placed inside of a Zone do not move when the Zone shape is moved), but needs further testing to confirm after container=0 is set for all Zone shapes.
To Reproduce
Steps to reproduce the behavior:
Go to online drawio version 24.8.6
Click on More Shapes and IBM Cloud
Select Access Group in Groups category and add to canvas
Drop Virtual Server in Compute category onto Access Group on canvas
Move Access Group around
Virtual Server should not move with Access Group
Expected behavior
Shapes placed inside the Zone do not move when the Zone shape is moved.
Using container=0 for all Zone shapes prevents ambiguities. For example, in the screenshot attached, the App VSI is in App Subnet and App Security Group and Maint Security Group, but we don't want the App VSI to move if a Security Group is moved, the App VSI should only move if the App Subnet is moved.
Screenshots
draw.io version (In the Help->About menu of the draw.io editor):
draw.io version 24.8.6
Desktop (please complete the following information):
OS: Mac
Browser [Firefox]
Browser Version [132.0.1]
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
yes
Additional context
None.
The text was updated successfully, but these errors were encountered:
Preflight Checklist
You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should reporting bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
Per discussion in feature request 3914 if you could please ensure that container=0 is set for all Zone shapes and verify that shapes placed inside the Zone do not move when the Zone shape is moved. Thanks!
This applies to all Zone shapes:
Based on release 24.8.6:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Shapes placed inside the Zone do not move when the Zone shape is moved.
Using container=0 for all Zone shapes prevents ambiguities. For example, in the screenshot attached, the App VSI is in App Subnet and App Security Group and Maint Security Group, but we don't want the App VSI to move if a Security Group is moved, the App VSI should only move if the App Subnet is moved.
Screenshots
draw.io version (In the Help->About menu of the draw.io editor):
Desktop (please complete the following information):
I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:
Additional context
None.
The text was updated successfully, but these errors were encountered: