Must be nested inside a <core:page> tag.
]]>This will also be used as an anchor when generating links to the task. This ID is also used to generate the filename for the persistence XML file. If not provided, is generated from the label. Ids generated from labels will be unique, but may change as page structure changes.
]]>Defaults to the page short title.
]]>If a recurring task, this is the first date it occurs. Required for recurring tasks. Format is "YYYY-MM-DD".
]]>When recurring, tasks must be flagged as Completed/Nothing To Do/Missed for each of the scheduled dates.
Supported values are as documented in com.aoapps.hodgepodge.schedule.Recurring.parse method: Recurring JavaDocs
]]>false (the default) - recurring tasks are based on fixed time intervalstrue - recurring tasks are relative to previous time the task was Completed, Missed, or Nothing To Do.
Must be the name of a User.
Defaults to "Unassigned".
To provide multiple assignments, use nested <task:assignedTo> tags.
This is free-form, could be anything, such as "$1000" or "$120/hr".
]]>This is free-form, could be anything, such as "$1000" or "$60/month".
]]>Defaults to "medium". To provide multiple priorities use nested <task:priority> tags.
Supported values are:
Must be nested inside a <task:task> tag.
]]>
Must be the name of a User.
At least one person must be assigned the "0 days" task. Accepts format of:
Defaults to "0 days".
]]>Must be nested inside a <task:task> tag.
]]>Supported values are:
One and only one priority may be assigned the "0 days" task. Accepts format of:
Defaults to "0 days".
]]>When two tasks must be performed on the same day, they will be ordered based on the "doBefore" settings. By providing these value, this task will be scheduled after the other tasks. At least one of page or task must be provided. Must be nested inside a <task:task> tag.
]]>Defaults to the book of the current JSP file.
]]>If not provided, assumes the current page.
]]>Not allowed to reference task by generated id, set an explicit id on the task.
]]>Must be nested inside a <task:task> tag.
]]>Must be unique per task.
]]>null for none.
The statuses is a comma-separated list of statuses to match.
]]>Returns the map of statuses, in the same iteration order as the provided tasks.
]]>Returns the map of doAfters, in the same iteration order as the provided tasks. If no doAfters for a given task, will contain an empty list.
]]>
Resolves the new user and sets the cookie.
A empty username will result in the null user.
The cookie is not actually set when exporting,
as set by the X-com-semanticcms-core-exporting: true header.
When allUsers is non-null, adds users to the provided set.
Otherwise creates a new set.
Returns the set of all users.
]]>Scheduled tasks are before unscheduled within a single priority.
Priority inheritance: Tasks will inherit any higher priority from tasks that either directly or indirectly must be done after the task. For example, a low priority task that must be done before a high priority task will be treated as high priority.
If dateFirst is true, will sort by date then priority. Otherwise
sorts by priority then date.
Filters for user or all when user is null.
Filters for user or all when user is null.
Filters for user or all when user is null.
Filters for user or all when user is null.
Filters for user or all when user is null.