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
WHAT does the new feature mean or enable?
It enables visitors of a website to enter a task description into a web form. On execution of Taskwarrior it checks for new tasks in pipeline from the web form, asking the user either to accept or to reject the task.
WHICH new reports are required needed?
None.
WHO benefits from this feature?
The Taskwarrior user does not require to enter the task from an external source. Instead, the user is required to reject or accept the task (or modify it as per his wish). Optional: The creator of the task can subscribe to the task status: He may be notified of acceptance, rejection, change, start, stop, done status via RSS feed or email.
HOW does the feature interact with existing features?
A config file setting enables Taskwarrior to parse a given URL which contains the backlog of external task wishes on execution. The user is required to accept or reject each task listed in this file. Thus, it is a distinct feature which may call the mod command. It may increase the code rucksack significantly and should therefore be considered as a plugin.
HOW does the feature retain the simplicity and efficiency of the core features?
It's a plugin.
HOW can I make others realize they cannot live without it?
Code it, test it, experience it.
Is my feature any more than just a built-in UDA?
Yes: It connects a web form to taskwarrior with feedback cycle on the specific task status.
The text was updated successfully, but these errors were encountered:
Benjamin Weber on 2013-11-20T18:58:06Z says:
WHAT does the new feature mean or enable?
It enables visitors of a website to enter a task description into a web form. On execution of Taskwarrior it checks for new tasks in pipeline from the web form, asking the user either to accept or to reject the task.
WHICH new reports are required needed?
None.
WHO benefits from this feature?
The Taskwarrior user does not require to enter the task from an external source. Instead, the user is required to reject or accept the task (or modify it as per his wish). Optional: The creator of the task can subscribe to the task status: He may be notified of acceptance, rejection, change, start, stop, done status via RSS feed or email.
HOW does the feature interact with existing features?
A config file setting enables Taskwarrior to parse a given URL which contains the backlog of external task wishes on execution. The user is required to accept or reject each task listed in this file. Thus, it is a distinct feature which may call the mod command. It may increase the code rucksack significantly and should therefore be considered as a plugin.
HOW does the feature retain the simplicity and efficiency of the core features?
It's a plugin.
HOW can I make others realize they cannot live without it?
Code it, test it, experience it.
Is my feature any more than just a built-in UDA?
Yes: It connects a web form to taskwarrior with feedback cycle on the specific task status.
The text was updated successfully, but these errors were encountered: