Whether you import data from apps like Jira and Asana or manually input data into Visor, you can display nested data (e.g., parent + child relationships).
In this article, we'll cover:
- Overview of Nested Data in Visor
- How to Import Nested Data
- "Levels Shown" for High-Level or Granular Views
- How to Change the Order of Nested Records
Overview
Project management apps like Jira and Asana (which Visor connects to) offer nested data because they help teams build out project plans in an organized way.
Visor imports from these apps, allowing you to create visualizations that can show either a high-level view of your data (by filtering out smaller tasks like "subtasks") or more granular views (by including these smaller tasks).
Below is an example of a Table view that has nested data:
How to Import Nested Data from Jira, Asana, and Salesforce
When you import data from apps like Jira, Asana, and Salesforce, Visor will honor how you structured your data.
For example, if you’re using apps like Jira, you probably use a combination of Epics, User Stories, Tasks, Subtasks, Bugs, and possibly more. Asana users might be more familiar with Tasks and Subtasks. Visor will honor how you structured data while importing it.
1. For Jira Users:
When you import your Jira and into Visor, you’ll be presented with the option to either "Maintain nesting from Jira" or "Ignore nesting from Jira".
2. For Asana and Salesforce users:
Visor will automatically import your nested data.
What to Expect When Data Imports:
When Visor imports your nested data, you’ll notice a combination of parent and child records appear in your workbook.
While Visor is flexible enough to allow you to modify nested relationships or use a completely flat hierarchy for your Jira Issues, please note that these changes will not reflect in Jira if you sync back to it. Additionally, if you import after making any changes, they may be reverted to reflect the original hierarchy set in Jira.
Levels Shown for High-Level or Granular Views:
Levels Shown Feature
Once you import or input your nested data into Visor, you can decide how much granularity you want to show in your various views. For example, if you have Asana or Jira data, you can decide to exclude "Subtasks" in a view like a Table or Gantt.
Typically, high-level views like roadmaps don't show as much granularity. In contrast, more tactical views (e.g., backlog refinement) do.
Configuring levels shown in Table & Gantt views
Table and Gantt views allow you to view all or a subset of all the levels which exist in your data. Simply click on "Levels Shown" to decide the levels you want displayed.
Update levels shown to only display the levels you care about via following steps:
- Click on the Levels Shown option
- Update the selections in that menu
- Save the Levels Shown settings
If you’re looking at Jira data, you may have one level dedicated to Epics, and subsequent levels dedicated to User Stories, Tasks, and Bugs. You might even have a further level dedicated to Subtasks. You can choose any or all of these topions.
Configuring Levels Shown in the Timeline view
You can find "Levels Shown" in the same as for Timeline. However, unlike Table and Gantt, you won't be able to select multiple levels (only one).
Because the Timeline view is built for targeted analytics, it allows you to view one level at a time:
Update levels shown to display the level you care about through via following steps:
- Click on the Levels Shown option
- Update the selection in that menu
- Save the level shown settings
Whether you want to gauge your tactical performance of individual User Stories or are reporting to executives on the strategic progress of your Epics - you’ll be able to easily select the level that makes the most impact on your audience.
Configuring Levels Shown in the Dashboard view
The Dashboard view offers a "Filter" option that allows you to select the level of granularity you want displayed in your Dashboard view's charts.
How to Filter Your Dashboard:
1. Click "Filters"
2. Select "Issue Type" for Jira (or equivalent for other connected apps / manually inputted data)
3. Choose the types of issues/tasks you want displayed
How to Change the Order of Nested Records
Nesting records by dragging
Whether you’ve imported from Jira, Asana, or Salesforce, or are inputting your data directly into Visor - you can manually nest records in Visor.
To use this feature, hover over the nesting level (left-most) column, click on the gripper icon, and drag a record to be a child of another record. Green indicators show where the target position will be as you drag the record.
Nesting records using the “Parent” field
When nested records already exist in your workbook, you can quickly change the parent + child relationship for one or multiple records.
To use this feature, select the corresponding record cell for the parent field and type in the primary label for the new parent it should be a child of.
To update multiple records under a new parent, you can copy (ctrl/cmd + C) the value of the target parent value, highlight all the parent cells for the records you want to move, and paste (ctrl/cmd + V) the value.
You can update nesting in Table and Gantt views.