Interact with Tasks directly from Release Package Hot

https://serenacentralphotos.s3.amazonaws.com/original/86/5f/69/image-72-1448620809.png
by David Berner on November 27, 2015

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 taks 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.

  • Please login to view any attachments.

  • Already have an account? or Create an account
    David, manual tasks process may be changed, so we may need to perform several additional transitions in order to either fail or complete it. Some of transitions may contain required fields. Are you expecting Release Control to move manual task through workflow generating dialogs for entering required fields? Would it be fine to just mark corresponding task as completed in Release Control, but in SBM it would remain unchanged?

    Another possible idea is to add hidden transitions to be able to complete or fail manual task from any state available only to Release Control, so we would have tracebility of what happened to manual task.

    Do you have any thoughts on implementation details of feature you are asking?
    Yuri Dmytriev Commented by Yuri Dmytriev May 12, 2016
    Top 100 Reviewer  -  

    David, manual tasks process may be changed, so we may need to perform several additional transitions in order to either fail or complete it. Some of transitions may contain required fields. Are you expecting Release Control to move manual task through workflow generating dialogs for entering required fields? Would it be fine to just mark corresponding task as completed in Release Control, but in SBM it would remain unchanged?

    Another possible idea is to add hidden transitions to be able to complete or fail manual task from any state available only to Release Control, so we would have tracebility of what happened to manual task.

    Do you have any thoughts on implementation details of feature you are asking?

    I Agree with Vickie, having the interactions with email may give an acceptable workaround for some situation, but it would not address the issue entirely. I like the idea of a menu giving direct access to the task interactions.

    I am sure there are other ways you could think about integrating these in a standard way without "messing" with the actual layout of the release package.
    David Berner Commented by David Berner April 25, 2016
    Top 10 Reviewer  -  

    I Agree with Vickie, having the interactions with email may give an acceptable workaround for some situation, but it would not address the issue entirely. I like the idea of a menu giving direct access to the task interactions.

    I am sure there are other ways you could think about integrating these in a standard way without "messing" with the actual layout of the release package.

    I love this idea David. Another UI design might be something like this: Put an "actions" link next to the task's status. When you click on Actions, a small menu could appear with the different transitions (start/complete/reject/etc). That would save some space on the screen but would still look nice, like the "more" button on the toolbar today.

    An email notification wouldn't really be the same. With email, you still have to leave the Release Package to go somewhere else. The key is to stay on the release package with less movement and clicking around.
    Vickie Ortega Commented by Vickie Ortega April 22, 2016
    Top 50 Reviewer  -  

    I love this idea David. Another UI design might be something like this: Put an "actions" link next to the task's status. When you click on Actions, a small menu could appear with the different transitions (start/complete/reject/etc). That would save some space on the screen but would still look nice, like the "more" button on the toolbar today.

    An email notification wouldn't really be the same. With email, you still have to leave the Release Package to go somewhere else. The key is to stay on the release package with less movement and clicking around.

    David, have you considered setting up email notifications, so owner of a task would receive notification automatically. In this case you need a click(1) to start a release package deployment, click(2) to navigate to first task from email, click(3) to transition first task to a final state, click(4) to navigate to second task from email, click(5) to transition second task to a final state. So you would need same 5 clicks.
    Yuri Dmytriev Commented by Yuri Dmytriev February 10, 2016
    Top 100 Reviewer  -  

    David, have you considered setting up email notifications, so owner of a task would receive notification automatically. In this case you need a click(1) to start a release package deployment, click(2) to navigate to first task from email, click(3) to transition first task to a final state, click(4) to navigate to second task from email, click(5) to transition second task to a final state. So you would need same 5 clicks.

     

PrintEmail