View Single Post
We call each of those "rows" a swim lane internally, to disambiguate from a row of tasks that may lay out one after another in the same vertical range.

Two factors determine the height of a swim lane. The first is that it must have vertical space to lay out all the tasks at their appointed time without overlapping. See attached. The portion of your plan shown is somewhat atypical in my experience in that it requires only one row.

The other factor is simply the resource name. We just want to lay it out sideways to label the swim lane. We ought to look into wrapping or truncating long names, and/or add resource initials that can optionally be used to label swim lanes. Could it work for you to shorten your resource names as a stopgap measure?

And please send a feature request to us at and let us know how you'd prefer to see this handled in the future.

Attached Thumbnails
Click image for larger version

Name:	Screen Shot 2011-08-09 at 2.54.42 PM.png
Views:	367
Size:	9.6 KB
ID:	1993