tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/603-subtasksLighthouse: Discussion 2011-04-09T00:34:28Ztag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-06-25T18:34:13Z2010-06-25T18:34:13ZSubtasks<div><p>Thanks for the suggestion. We're currently undergoing a
complete<br>
rewrite/redesign of this area, and I hope to have some good news
for you in<br>
the coming months.</p>
<p>Courtenay</p></div>Tiger Teamtag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-07-10T18:18:33Z2010-07-10T18:18:35ZSubtasks<div><p>I mocked up my ideal Project Management tool. I may have this
coded for myself, but I figured I would share it with you as
well.<br></p>
<p>I create all my specs in Backpack. I think of a Divider as a
task and all notes under that Divider as the subtasks. The way I
have this speced out, I would still do all my authoring in
Backpack. My Tasks and Subtasks would be pulled in to this new app
as tickets that I could assign and track. Here is an example
Backpack<br>
<a href=
"http://matchbooktest.backpackit.com/pub/2046762-backpack-import-test">
http://matchbooktest.backpackit.com/pub/2046762-backpack-import-test</a></p>
<p>Why do I do it this way? I have a hard time envisioning and
working on a product when it's broken into tasks. I need to see the
entire thing at once, quickly move around, and be able to cross
reference. I also want a master document that I can refer back to
in the future. Tickets hinder all of this. On the other hand,
developers don't like to work with a giant list so they need things
broken down.</p>
<p>Maybe the attached mock will influence your designs.</p></div>Jason Schwartztag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-07-10T19:06:28Z2010-07-10T19:06:28ZSubtasks<div><p>That's nuts.. (in a good way!) looks like you've put a lot of
thought<br>
into it. We're actually working on a "social" task/todo app<br>
(tentatively called Today) that combines scheduling and ticketable
items.. I'll let you know once there's something to look at.</p>
<p>I'm also a really visual/spatial thinker so I like to be able to
zoom<br>
out and group tickets by task or "mission".</p></div>Tiger Teamtag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-07-10T19:23:26Z2010-07-10T19:23:29ZSubtasks<div><p>Thinking about it in terms of being a visual/spatial thinker and
visualizing an entire project is interesting. That is what I was
getting at, but I didn't think about the reasoning behind where
that 'want' was coming from.<br></p>
<p>Having another word like Mission to describe a grouping is a
great idea. The connotation of Task is too specific. Definitely
send me Today when it's ready. It sounds interesting and is the
thing that Basecamp is missing.<br></p></div>Jason Schwartztag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-07-10T19:39:46Z2010-07-10T19:39:46ZSubtasks<div><p>We're prrrrrrrobably doing something called missions in the
next<br>
version of lighthouse, where you can bundle up a bunch of
tickets<br>
together (separately to their organization in a milestone).
Maybe.<br>
There's a battle back and forth between me and the designers on
this<br>
feature :) Trying to keep things simple is the hard part.</p></div>Tiger Teamtag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-07-10T21:08:16Z2010-07-10T21:08:16ZSubtasks<div><p>I think I would organize Missions like this.</p></div>Jason Schwartztag:help.lighthouseapp.com,2008-09-20:Comment/20797932010-07-10T21:28:09Z2010-07-10T21:28:09ZSubtasks<div><p>in Option 2, I forgot to note that Sort would only sort within
Missions. The alternative would be to have a Flat/Hierarchy view
switch, but that's starting to sound complicated and
unnecessary.<br></p></div>Jason Schwartz