You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
The text was updated successfully, but these errors were encountered: