task macro

Overview

The {task} macro is used to automatically create tasks when a workflow {state} is entered.

Optional.

One or more {task} macros can be put in a {state} macro.

Within a {state}, each {task} must be uniquely named.

Parameter	Notes	Ver
unnamed first parameter or `name`	Name of task: Within any `{state}` macro, each `{task}` macro must have a unique name The name can use any character set supported by your Confluence server – except some reserved characters.	3.0+
`assignee`	Task assignee: Username – must have edit permission on the associated content Supports Value References If no assignee specified, any user with edit permission on the associated content can assign or complete tasks. Content by label There is no content with the specified labels	3.0+
`duedate`	Due date for task completion: Format can be either: Explicit date in the format: `YYYY-MM-DD HH:mm` (v4.12+) ISO 8601 Duration Period See Expiry Dates for more information Supports Value References If specified, the task, if not completed, will eventually expire and trigger a `taskexpired` event. Content by label There is no content with the specified labels
`note`	Note to associate with the task: Plain text Can use any character set supported by your Confluence server – except some reserved characters. Logged in activity report and sent in notifications Content by label There is no content with the specified labels	3.2.7+
Deprecated The following parameters are no longer supported.
~~`type`~~	OBSOLETE Task types are no longer supported – use {approval} macros instead, with customised button labels.	3.0 ↓ 3.2

A {state} can be configured to automatially transition once all tasks are completed via its completed parameter.

The following Events relate to tasks:

{workflow:name=Task example}
   {state:Tasks|completed=Done}
      {task:Some task}
   {state}
   {state:Done}
   {state}
{workflow}

Content by label

There is no content with the specified labels