wildbee/wildbee — pull request #4 by mtjandra (2013-11-10 22:20:25+00:00)
Title: Testing tasks

Still incomplete but thought it would be good to share so other's can review/contribute.
You may need to drop and re-create the wildbeehive database.

Currently tasks have state to test state changes, this will later be moved to packages.
Currently workflow definition is represented as a comma separated string.
Currently not yet implementing uuids.
Currently needs validation checks.
(Ex. If you change the work flow from A -> B -> C to A -> E -> F
What happens if your package was in state B?)
Currently workflows with duplicate elements are not supported
(Ex. A -> A -> C
Will be stuck in state A)
Please do not use the "Delete a Task", task view is not made to handle this right now, but your task should be deleted in DB.

To play around with the current utilities
1) Create a user at /formtest
2) Create a task at /tasks
owner: Refers to owner ID (Use 1 to refer to the user you created at step 1)
task: Refers to the name of the task you want to create
Default workflow is Open -> In Progress -> Closed
3) Change state of a task
owner: Refers to the task ID
task: Refers to the task Name
When you hit update task you should see the state change from Open -> In Progress
4) Change the workflow
Set your stages with the combo boxes
Ensure all stages are unique
Ensure your task is in one of the stages you defined in the workflow
Hit update status
Test state changes as in step 3

Again still incomplete and in testing, just opening up for suggestions and so others can learn/contribute.