Hi, I installed tracks and I like it a lot so far.  I was going to enter a new ticket for desired functionality, but after clicking “New Ticket” on the dev site it wasn’t clear how to get permissions to add a ticket without already having permissions.

I did go through some of the open tickets and I haven’t seen the same suggestion there so here goes:  Could you allow for “non-actionable” actions in your system?  This would involve the addition of a boolean for every action, but I think it would increase the functionality of the system in several ways:

1) You could say that all projects and actions that are “non-actionable” belong in the “someday/maybe” category and can get their own tab in the UI.
2) You could load up a project with “non-actionable” actions and it will default to “someday/maybe” until you pick an action to do next.
3) No need to clutter up the home page with “non-actionable” items, or items that are really depend on other actions.

Using your system I keep wanting to add “non-actionable” steps to the projects that I have - I think it’s a valuable brainstorming exercise when I do reviews.  Although I can stick them in a “Someday/maybe” context, really these items shouldn’t be on the main page with actionable items.  During review it’s more valuable to see all the “someday/maybe” in projects rather than in individual actions.

It appears you’ve already added the concept of “start date” in the development trunk.  I’m not sure if this is more or less elegant that adding a boolean, but you could also say that an action with a null “start date” is non-actionable, and that an action that has a start date of today is currently actionable, so without adding to your schema you could implement all this.

I know you’ve had requests for action dependencies, and perhaps you’ve already implemented them, but for me “non-actionable” items would be more useful.  Often when you do an action, you find out you have to do another action before you can get to a dependency.  If you do implement action dependencies I hope your UI makes it easy to insert prerequisite steps that may pop up.

Thanks for a wonderful app!

-Don

Hi Don,

I think most people accomplish what you’re looking to do by creating a someday/maybe context and assigning non-actionable items to that context and to whatever project they logically belong to.

Does that address the first part of you question?

BTW, to create a ticket on the Trac:

NOTE THAT BECAUSE OF SPAM, YOU NOW NEED TO LOGIN (user=guest, pass=guest) TO SUBMIT OR COMMENT ON TICKETS.

Cheers,
Luke

Thanks for responding Luke,  I’ll add a ticket next time.  I suppose you could implement most of what I’ve suggest by making the “Someday/maybe” context special in the UI and separating out projects that only have actions that are marked “Someday/maybe”.  I do believe I saw a few tickets that ask for “Someday/maybe” to be a special context.  But I think it’s conceptually cleaner to have an actionable/non-actionable flag instead of a hard-coded context.

Cheers,
Don

Michael Langford suggested (and is having a go at implementing in a patch) having a third state for projects: ‘pending’. So there would be active, completed and pending. I hope that will scratch your itch!

Adding another state for projects was exactly what I was thinking. I was going to suggest a “Someday” to be added to the Active, Completed, and Hidden options.