For initial beta, each deliverable type will have its own basic workflow. It is attached to the deliverable type at time of project/deliverable creation. It is started at time of create of the project/deliverable.
This will be a workflow called "Web Banner Tasks"
Have the following nodes
Create Initial Media
Creative Approval
Legal Approval
Finalize items
Each node needs to have a due date and assignee(s) All steps are initially set to the Project Admin(s). due date(s) is not set.
There are no lifecycle transitions handled by the wf.
AC:
- Each step can be skipped
- The initial assignee of a step is the project admin(s)
- The due date is empty by default on each step
- is related to
-
NBM-246
As a Project Admin, I know a task is completed
-
- Resolved
-
-
NBM-247
As a project member assigned to a task, I can choose to complete or reject a task and include a message on the task when I am finished.
-
- Resolved
-
-
NBM-245
As a Project Admin, I can choose to skip a step on a workflow
-
- Closed
-
-
NBM-243
As a Project Admin on the deliverable view, I can assign a wf task to a project member and define a due date
-
- Resolved
-
1.
|
Create Workflow definition in Studio |
|
Resolved | Gildas Lefevre |
|
|||||||
2.
|
Create Unit tests to validate the workflow |
|
Resolved | Gildas Lefevre |
|
