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
When clicking on information about a node, e.g. "Outbound Control", a graph is rendered with this information. In Legacy BloodHound the query used to gather this information was shown in the raw query field.
This can be useful if you want to have a base query, you can start to edit to your own needs.
Current Behavior:
The graph is created but the used Cypher query is lost.
Desired Behavior:
When clicking on node information that provide a graph, e.g. "Inbound Control", "Outbound Control", "Member Of" or "Execution Privileges", the executed query should be shown in the query editor.
Use Case:
When analyzing data, I often start with a base query from the UI and extend or limit the information that the query returns, based on my needs. For a quicker workflow it is convenient to be able to edit an existing query.
The text was updated successfully, but these errors were encountered:
Feature Description:
When clicking on information about a node, e.g. "Outbound Control", a graph is rendered with this information. In Legacy BloodHound the query used to gather this information was shown in the raw query field.
This can be useful if you want to have a base query, you can start to edit to your own needs.
Current Behavior:
The graph is created but the used Cypher query is lost.
Desired Behavior:
When clicking on node information that provide a graph, e.g. "Inbound Control", "Outbound Control", "Member Of" or "Execution Privileges", the executed query should be shown in the query editor.
Use Case:
When analyzing data, I often start with a base query from the UI and extend or limit the information that the query returns, based on my needs. For a quicker workflow it is convenient to be able to edit an existing query.
The text was updated successfully, but these errors were encountered: