#185

Add support for follow-up/sequential actions.

    • Created on: Sun, Jan 01 2006 (over 6 years ago)
    • Reported by: Anonymous
    • Assigned to: bsag
    • Milestone: Someday/Maybe
    • Type: -
    • Resolution: -
    • Version: -
    • Status: Fixed
    • Priority: Normal (3)
    • Component: Functionality (app)
    • Estimate: None/Small/Medium/Large None
    • Severity: -
    • Keywords: -
    I find that when I create a project, I often come up with several future actions. However, these actions are sequential, i.e. action 3 depends upon the completion of action 2, action 2 on action 1, etc. As such, I only want to see the next action (action 1), and not the follow-up actions (2,3). Looking through previous tickets, I noticed that others have requested a similar feature, though it appears that the current version of Tracks (svn revision 170) does not yet support this.

    After (briefly) looking through the code and the database, I thought of one way that this might be implemented. Two new columns could be added to the 'todo' table: 'active' (a boolean which could prevent display) and 'predecessor_id'(or something similar). An existing action would then have a link to create a follow-up action; the follow-up's predecessor_id would be set to that of the existing action, and would be marked as inactive. When the existing action is marked as done, it would look for any follow-up actions and mark them as active (hence one action could have multiple follow-ups).

    The active/predecessor_id columns could also be added to projects, so that projects could be treated in the same fashion. One issue here, though, would be determining if a predecessor_id refers to an action or a project.

    A side benefit of adding an active flag to actions/projects is that it could also be used to for the Someday/Maybe context; any actions/projects added to Someday/Maybe could be marked as inactive so that they are not shown in the 'Home' display.
  • Followers
     
    Ico-users bsag (Assigned To) 
     
    Attachments
    No attachments
    Associations
     
    # Relation Summary Status Action
    Activity
     
    User picture

          on Jan 04, 2006 @ 08:15am UTC * By Anonymous

    Status changed from New to Accepted
    Yes, this is a popular request! At the moment I'm working on getting the Ajax parts of the interface really solid and reliable, and then I'll work on a tickler (getting next actions to appear only when a certain date arrives) and these dependencies. I'll most likely try to integrate them, because they both involve hiding an action until something else happens (a date passes or another action is completed).
    User picture

          on Feb 04, 2007 @ 06:31pm UTC * By Anonymous

    Milestone changed from 2.0 to -none-
    User picture

          on Jan 08, 2009 @ 10:16am UTC * By lrbalt

    Milestone set to Someday/Maybe
    Updating tickets (#373, #105, #107, #117, #125, #126, #147, #177, #182, #183, #185, #197, #202, #206, #220, #236, #240, #276, #283, #294, #300, #305, #309, #312, #317, #324, #337, #357, #358, #360, #433, #452, #462, #17, #74, #82, #92, #123, #265, #431, #440, #475, #94, #256, #258, #464)
    User picture

          on Aug 11, 2010 @ 08:39am UTC * By lrbalt

    Status changed from Accepted to Fixed
    dependencies are implemented in current master tree
    Time Expenditure
    Loading