#78
  • Created on
    2005-07-12 00:55
  • Reported by
    Anonymous
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    bsag
  • Milestone
    -
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

Ability to hide actions due beyond a certain date

It would be nice if there was a configurable option that would allow me to only show actions that are undated or due in the "N" days. I have a lot of actions that are 2+ weeks out that are not urgent enough yet to be on my radar screen.

A great way to configure this would be with dynamic AJAX dropdown box on the tasks page.
User picture
  on 2005-07-12 04:27 *
By Anonymous
Status changed from New to Accepted
Status changed from New to Accepted
I have something that would fulfil much the same function slated for "1.10":http://dev.rousette.org.uk/roadmap -- the tickler. The plan would be to allow you to set a date when you want an action to appear on your list. Before then, it sits in on a separate 'tickler' page (which you can view, edit, etc.). That allows you to get stuff off your mind now which needs to be done some time in the future, but not have it cluttering up your list yet.

I'm actually hoping to add that as the next main feature, after Nic has finished the multi-user stuff.
User picture
  on 2005-09-29 05:37 *
By Anonymous
that would be a very nice feature.
And it would fit a bit more into the GTD concept ("out of sight" here). I already missed the "43 folders" part which can't be integrated so far. Probably a "tagging feature"#48 would fit in this case also?
User picture
  on 2005-09-29 05:40 *
By bsag
that would be a very nice feature.
And it would fit a bit more into the GTD concept ("out of sight" here). I already missed the "43 folders" part which can't be integrated so far. Probably a "tagging feature"#48 would fit in this case also?
User picture
  on 2006-05-02 13:16 *
By bsag
Status changed from Accepted to Fixed
Status changed from Accepted to Fixed
A solid start on this has been made in [232]: it will be improved with time, but the basic functionality works as you described. See the changeset [232] for details.