Bug: Sequential layout not working for isolated nodes

[rtpt-romankarwacik]

Description:

The different layout options for isolated nodes are the same, for example isolated nodes with sequential layout:

In contrast to nodes with relations in the view in sequential layout:

Are you intending to fix this bug?

no

Component(s) Affected:

• UI

Steps to Reproduce:

1. Go to Cypher
2. Enter query:

MATCH p=(n:User)-[:MemberOf]->(g:Group)
RETURN g
LIMIT 10

4. Layout -> Sequential
5. Nodes are arranged in the same way

Expected Behavior:

Nodes should be in a list-like sequential layout like when they have an edge to another node, similar to:

Actual Behavior:

Nodes are arranged in the same way as in the standard layout.

Environment Information:

BloodHound: 6.3.0

Browser (if UI related): Firefox 134.0.2

Node.js (if UI related): 18.19.0

Contributor Checklist:

• I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
• I have provided clear steps to reproduce the issue.
• I have included relevant environment information details.
• I have attached necessary supporting documents.
• I have checked that any JSON files I am attempting to upload to BloodHound are valid.

[StephenHinck]

@rtpt-romankarwacik - in your first screenshot, your query returns the variable g, the group objects matched in your filter. In the second, it returns p, the full pattern. If you change your query to return p in both cases, you should get the expected results. The latter query only returns individual objects, so the visualization library has no relations against which to organize.

[rtpt-romankarwacik]

This was only used as an example, where in the first screenshot only nodes were returned, and in the second paths were returned. I could also have chosen another example for the first query, e.g.:

MATCH (n:User)
RETURN n
LIMIT 10

The problem is that if ONLY nodes are returned, and no paths/relations, the sequential layout is the same as the standard layout

[StephenHinck]

Got it. @rtpt-romankarwacik - in future versions, we plan to have this result default in a tabular view of data, rather than a bunch of dissociated nodes on the canvas. This would let you display consistent columns of properties associated with the nodes (for example, if you were looking for users who haven't rotated passwords, the "Password last rotated" field would likely be valuable to display).

Unfortunately, the graphing library we use doesn't provide "out of the box" support for what you're requesting, so it would take some work to add that functionality. However, I believe the tabular view will provide a better experience anyway.

Let me know your thoughts!

[rtpt-romankarwacik]

A tabular view sounds like a nice solution 👍