[chandler-users] Collection organization, or subcollections
cubranic at cs.ubc.ca
Wed Jan 30 15:28:42 PST 2008
This being a commonly requested feature, there exits a Bugzilla bug for
it (bug number 5058). See
You can subscribe to the bug from this page if you want to track its
progress, add comments, or even contribute code to implement the fix.
P.S. It's usually worth searching the Bugzilla to see whether your issue
has already been reported.
On Wed, 30 Jan 2008, Mimi Yin wrote:
> Hi Mikolai,
> I just realized that I've had this email flagged for the past month, but I'm
> not sure if anyone got back to you.
> You are not the first user to pipe up with this request. Thanks for taking
> the time to write in. At this time, I can't make a promise about when this
> feature will appear in Chandler, but we are aware that this is user need we
> should address soon.
> On Dec 21, 2007, at 10:01 AM, Mikolai Fajer wrote:
>> First off, I really appreciate the thought and hard work put into making
>> Chandler a great product. I am new to the GTD scene, so if my questions
>> are anti-GTD please enlighten me!
>> My current Chandler collections are:
>> I would like to make a hierarchical scheme:
>> ---Project 1
>> ---Project 2
>> ---Class 1
>> This strategy would help me keep my focus on the appropriate scope. For
>> example, at work I would never need to go above the Work Dashboard. I
>> recall reading something about Chandler and subcollections, but I cannot
>> find it again. Are there any thoughts on this feature/strategy? Thanks!
>> -Mikolai Fajer-
>> chandler-users mailing list
>> chandler-users at osafoundation.org
> chandler-users mailing list
> chandler-users at osafoundation.org
More information about the chandler-users