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 understand that AWX is open source software provided for free and that I might not receive a timely response.
Feature type
Enhancement to Existing Feature
Feature Summary
When editing workflows in the visualizer, the UX leaves something to be desired.
As an example:
The fourth job template going from the left is hovering over a success edge. this edge is hard to remove because the menu hides behind the template.
My request is to implement some sort of solution, which could be increased distance between nodes/edges or drag-n-drop of nodes, to make the experience a lot better.
Select the relevant components
UI
API
Docs
Collection
CLI
Other
Steps to reproduce
Create a Workflow template.
Create 3 nodes at least.
node1 -> node2 -> node3
then make node1 edge that continues to node3 on success, and a node1 edge that continues to node2 on failure. node2 edge to node3 on success.
node2 then hides the on success edge between node1 and node3
Current results
Sugested feature result
less problematic deletion/modification of edges, along with updates of nodes/templates that have had their variables updated.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Please confirm the following
Feature type
Enhancement to Existing Feature
Feature Summary
When editing workflows in the visualizer, the UX leaves something to be desired.
As an example:
The fourth job template going from the left is hovering over a success edge. this edge is hard to remove because the menu hides behind the template.
My request is to implement some sort of solution, which could be increased distance between nodes/edges or drag-n-drop of nodes, to make the experience a lot better.
Select the relevant components
Steps to reproduce
Create a Workflow template.
Create 3 nodes at least.
node1 -> node2 -> node3
then make node1 edge that continues to node3 on success, and a node1 edge that continues to node2 on failure. node2 edge to node3 on success.
node2 then hides the on success edge between node1 and node3
Current results
Sugested feature result
less problematic deletion/modification of edges, along with updates of nodes/templates that have had their variables updated.
Additional information
No response
The text was updated successfully, but these errors were encountered: