OnePager 6.1 and earlier traditionally supported a single level of swimlanes, enabling users to group rows together based on a single value. In OnePager 7.0, we have expanded to a total of three levels of swimlanes, which nest inside each other to better display the hierarchy of projects and programs.
When multiple swimlanes are used, the largest grouping will always be in the left-most swimlane, and smaller groupings will follow from left-to-right. In this example, we have three levels of swimlane:
- First Swimlane: Program
- Second Swimlane: Project
- Third Swimlane: Phase
When you upgrade from an earlier version of OnePager, your old swimlanes will be converted to the left-most swimlane in the hierarchy, so any new swimlanes that you add will be to the right of your original swimlanes unless you rearrange them.
Turning on Multiple Swimlane Levels
To turn on more than one swimlane level, go to Home > Chart Properties > Rows/Swimlanes.
In the redesigned Swimlanes section, there are three tabs: Left #1, Left #2, and Left #3:
Each swimlane level can group based on a different field from Microsoft Project or Excel. We recommend grouping swimlanes by fields that have a natural hierarchy relative to each other. For example, grouping by "Project Name", then "Level 1 Summary Name", and finally "Level 2 Summary Name" will cascade correctly, and your swimlanes will nest nicely within each other based on the data that you already have in Microsoft Project or Excel. You can, of course, select any field to drive any level of swimlanes, but keep hierarchies in mind when doing so.
The font for swimlane text and the overall width of swimlanes are also configurable in this same area. For more advanced swimlane formatting, including backgrounds, text rotation, and custom swimlane headings, click the Swimlane Formatting button, which will provided an expanded selection of settings, many of which are new in OnePager 7.0.
Each swimlane level can also be sorted independently. We recommend either sorting your swimlanes based on the order of your underlying project plan (Sort Swimlanes like Project/Excel) or sorting your swimlanes based on the same field that you used to group your swimlanes in the first place. For example, if your swimlanes are grouped based on "Text 1", you can sort swimlanes alphabetically based on "Text 1" as well. If you sort your swimlanes by a field that is different than the field you used to group your swimlanes, keep in mind that your sort order may not be what you expect, especially if each swimlane has a heterogeneous set of values in the sorting field compared to the grouping field.