Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next Action Dependencies #300

Closed
dnrce opened this issue Jun 25, 2014 · 0 comments
Closed

Next Action Dependencies #300

dnrce opened this issue Jun 25, 2014 · 0 comments
Milestone

Comments

@dnrce
Copy link
Member

dnrce commented Jun 25, 2014

Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/300

Projects are an excellent way of defining lots of next actions into a group with a singular goal, but what do you do about NAs that depends on another NA to be completed?

What i'm suggesting is a slight modification to the ticker system that currently exists in trunk, you can set a date for the NA to show on the main list OR when a certain NA has been completed. That way when you complete one NA on your main list, the follow-on NA will be transfered from the Tickler to the main list.

This feature would be an amazing timesaver, and i guess that other people would also like it implemented.

h3. Proposal for todo FSM with added pending state
!http://www.assembla.com/spaces/tracks-tickets/documents/dD_W-EIQar3QxReJe5afGb/download/todo_fsm.png!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant