Export Tree to CSV

In the toolbar, you will find the Export button. This feature is designed to export the visual tree structure into a CSV file, which can be used for reporting, offline analysis, or as a backup.

Functionality

Click on the Export button to initiate the download of the current tree structure.
The generated CSV file will encapsulate the hierarchical relationships, along with the item fields currently active in the tree.

Representation of the Hierarchical View in the CSV Export

The CSV file produced by the Export function presents the project's tree structure in a tabular format, where each item node from the tree is translated into a single row within the spreadsheet.

Key Points of the CSV Structure –

One Item Node Per Row: Every item node in the tree structure corresponds to one row in the CSV file. This one-to-one mapping ensures a clear and organized representation of each item from the Links Explorer. You can identify the node represented in the row by looking at the Item name column in the CSV.
Indent Level: The Indent Level column indicates the hierarchical position of an item within the tree. Items at the top level have a lower indent level, while nested items show a higher indent level, maintaining the parent-child relationships present in the visual tree.
Link Column: In the tree, item-nodes are visually connected by the link-nodes to denote board connections/links. In the CSV, this corresponds to the Link column which identifies the parent link-node of the item. This establishes the relationship between the item and its predecessor in the hierarchy.
Other Field columns: After the above tree specific columns, you will see the field values spread out as columns. Each item-node information field is represented as a column and its value for a row will be the corresponding value in that item node. If an information field is irrelevant to or absent in a node, the corresponding cell would be left empty.

Example

For example, let us consider the hierarchical view of item Create Banking app MVP - Beta –

Example Tree of Item Create Banking app MVP - Beta

When we export this tree, we will get the CSV file with the following content –

Let us examine the correspondence between the tree and the exported file –

You can see that each item in the tree has a row for itself.
You can see that each row has an indent value, that corresponds to its depth in the tree.
1. For example, Create Banking app MVP - Beta , the root node, has an indent level 1.
2. The next level item nodes have an indent level of 2. Similarly, their child item nodes would have an indent level of 3 and so on.
Consider the item nodes Create Banking app MVP - Beta and Login Methods.
1. Observe from the tree that Create Banking app MVP - Beta is connected to Login Methods by the Requires board connection.
2. Now, observe the CSV file. Here, we see that the row corresponding to Login Methods has the indent value 2, meaning that it is one level deeper than
  Create Banking app MVP - Beta(having level 1). But how do we know what the relation between both of these items is? This information lies in the Link column of the Login Methods row. The value of link column here is Requires, which corresponds to the connecting link node in the tree.
3. Along with Login Methods, observe that the nodes Export Transaction Report Formats, Supported Payment Methods are also transformed into rows with their indent level 2 and the parent link-node Requires set as the Link column value.
4. Similarly, the nodes Ability to link bank account and Ability to create UPI alias have their rows set to indent level 2 and their Link column value as Blocked by, which is their parent link node in the tree.
Alongside the Indent, Item Name and Link columns, you will find data columns of the item card spread out as columns. Looking at the Create Banking app MVP - Beta row, we can see its information fields: Assignee, Status and Priority.