While obviously most deployment tasks should be fully automatic, there are many use cases for manual tasks. We find that the current Release Package interface does not allow for smooth interaction with manual tasks and would like to propose a standardized way of how to integrate task level interactions directly on the release package form. Let me use the standard manual task project as an example:

1. create a release package containing two manual tasks
2. start deployment on the release package, the first task changes to "pending" state
3. in the deployment tasks tab, click on the title of the task
4. new window opens with the task status form. click on "start"
5. in the same window click on "complete" (or reject)
6. go back to the release package window
7. refresh the display if you have kept the window open --> the second task changed to "pending"
8. click on the title of the second task
9. new window opens with the task status form. click on "start"
10. in the same window click on "complete" (or reject)
11. go back to the release package window , refresh Here is what the flow could look like instead:

1. create a release package containing two manual tasks
2. start deployment on the release package, the first task changes to "pending" state
3. in the deployment tasks tab, simply click on "start" for the first task
4. the display refreshes, now choose between "complete" and "reject"
5. the display refreshes, now simply click on "start" for the second task
6. click on complete for the second task
7. the display refreshes, you can see that the release package is done

I counted 4 clicks instead of 10 for the task executions. All of this without leaving your window or even changing tabs. How could this be implemented?

1. in the task application, have a field where you list the transitions you would like to be "visible" from release package
2. in the release package, read this list, and display the available transitions in an additional column of the deployment task grid.
3. the display in the release package should refresh whenever a task changes state.

Maybe this could be done via a synchronous orchestration Anyway we will probably implement this in an ad-hoc manner, which will fix the usability case for us, but it would be nice if this mechanism would be provided out of the box.

Interested to hear your take on this.