2. Manage Task

Navigate to Task Design -> Tasks. Select Project and Release under which the task has to be viewed or edited. Select a task. Goto Overview tab.

• Overview Tab
  The following actions are available in overview tab:

  • Duplicate a task :
    Click on duplicate to create a duplicate copy of the task under the same Release.

  • Add to environment :
    Click on Tag to Environment to tag the task to an environment. The environments created for the release would be displayed, for user to select. Jiffy will allow to link the same task to multiple Environments. A task can be executed in Task Execution window only if it is linked to an environment.

  • Archive a task :
    Click on Archive to archive the task.  The archival will not be allowed if it is used as a child task in another task node.

  • Download csv :
    User can download the data pertaining to a task onto a csv file by clicking on Download CSV.

• Change History
  Click on Change History tab. Change History of a task is displayed here. For each version of the task, the details like version update, user etc are available for reference.

• Execution History
  Click on Execution History tab. High level details of Execution history is displayed here. This will populate the executions triggered from Task Execution window. i.e Trial Runs from Task Design will not be updated here. More details on execution history can be viewed in Task Execution -> Execution History.

• Check-in and Check-out from Repository
  Tasks can be added to repository using Check-in button from Task Design > Tasks. Prior to check-in, the task suite should be selected in Overview tab. Refer to Tasks -> Add Task. Once the check-in is selected for a task, it will not be updated into repository immediately. Instead it will wait for approval in Actionable -> Pending Requests – Update Repository until it is approved by a user who has the relevant authority.

To make changes to the task which is saved in repository, it needs to be checked-out in Task Design -> Task. This check-out feature ensures that only one person is editing the baselined task at a time. As long as one user is checking-in the task, others will not be able to check out the same.