Previous: Custom agenda views, Up: Agenda Views
Column view (see Column view) is normally used to view and edit properties embedded in the hierarchical structure of an Org file. It can be quite useful to use column view also from the agenda, where entries are collected by certain criteria.
To understand how to use this properly, it is important to realize that the entries in the agenda are no longer in their proper outline environment. This causes the following issues:
COLUMNS format to use. Since the
entries in the agenda are collected from different files, and different files
may have different COLUMNS formats, this is a non-trivial problem.
Org first checks if the variable org-overriding-columns-format is
currently set, and if yes takes the format from there. Otherwise it takes
the format associated with the first item in the agenda, or, if that item
does not have a specific format (defined in a property, or in it's file), it
uses org-columns-default-format.
CLOCKSUM property. Org will then sum the
values displayed in the agenda. In the daily/weekly agenda, the sums will
cover a single day, in all other views they cover the entire block. It is
vital to realize that the agenda may show the same entry twice (for
example as scheduled and as a deadline), and it may show two entries from the
same hierarchy (for example a parent and it's child). In these
cases, the summation in the agenda will lead to incorrect results because
some values will count double.
CLOCKSUM, that is always
the entire clocked time for this item. So even in the daily/weekly agenda,
the clocksum listed in column view may originate from times outside the
current view. This has the advantage that you can compare these values with
a column listing the planned total effort for a task - one of the major
applications for column view in the agenda. If you want information about
clocked time in the displayed period use clock table mode (press R in
the agenda).