Gridsz enables POs to configure their required status transition models for its tasks. This functionality is available to the cluster admin, therefore the status transitions & dependencies apply for the parties belonging to that cluster only.

If an task has a parent (InTask) and child tasks (OutTask), then for both the parent as well as the child(eren) a status transition will need to be configured. These do not have to match exactly, as only statuses which need to synchronise need to be configured in the Status dependencies.

Status Transitions

Status transitions configuration follows the following hierarchy for its setup:

• Domain (Passive Operator)
  • Module (e.g. Service)
    • Task type (e.g. Incident InTask)
    • Task subtype (if available)
      • Organizations (AO’s & Contractors)
        • Start Status
          • Status Transitions
          • Transition conditions
        • End Status(es)

Set up transition: define application of transition

When you setup a status transition, you are prompted with a pop-op that requires the following information:

• Name: of the status transition (free text)
• Domain: Passive Operator organization (pre selected when setting up)
• Module
• Task type
• Organizations: for what AO and Contractor parties does this transition apply
• Active/Inactive slider: to activate or deactivate this transition.

Once completed, select Next. You will be prompted to actually build the transition model:

• Start status: if the task is created what is the starting status of this task?
• End status(es): if the task reached this status the status transition model is considered complete and final. No further status transitions are possible, nor are any changes possibly any more on that task or ticket.
• Define transitions box: define as follows – add as many as you need (+ Add Transition).
  • From status
  • To status
  • Automatic: does it require a manual action?
  • Conditions (And/Or): if more than 1 condition, then:
    • all conditions have to be met before transition can happen: select And
    • if one of the conditions are met the transition can happen: select Or
  • [+]: Add condition, add if conditions apply for this transition

Once completed, select Save.

Transition boxes do not need to be setup in a fixed order. However, you are able to drag and drop them in an order that suits your needs.

Status Dependencies

The status dependencies functionality allows you to tie together parent and child (InTask and OutTask) status transitions for the same task type.

Gridsz will provide you with a single pop-up to setup your status dependency, choose a name (free text) for your dependency. Then use the dropdown to select two transitions to which the dependency applies. This means you need both a transition for the parent task as well as the child task.

Proceed to setup the dependencies in the parent and child config tabs.

please note that if you do not setup a status for OutTaskSet, the setup itself will be more simple but in the ticket/task no status is visible for the OutTaskSet.

• • InTask: Confirmed to WIP, then
  • OutTaskset: Confirmed to WIP, then
  • OutTask: Confirmed to WIP

Your OutTaskSet will have show the status WIP, like the OutTask.

• • InTask: Confirmed to WIP, then
  • OutTask: Confirmed to WIP
  • OutTaskset: not configured.

OutTaskSet will still show, but without any status, hence will not show WIP in this case.

Status Dependencies: Parent/Child config

The status dependency page contains two tabs, one parent config and one child config.

• Parent config
  Within the Parent config all the Parent to Child status transitions dependencies are configured.
• Child config
  Within the Child config all the Child to Parent status transition dependencies are configured.

For both config section the following setup is required to enable dependencies. Each + Add Dependency section consists of 2 rows and a condition section, add as many as you require. Do take into account the statuses that you have also setup and use within your status transition setups!
To setup you add:

• First row, FROM task type and status
  • Type (InTask/OutTask/OutTaskset), dropdown.
  • From status, dropdown.
  • To status, dropdown.
• Second row, TO task type and status
  • Type (InTask/OutTask/OutTaskset), dropdown.
  • From status, dropdown.
  • To status, dropdown.
• Conditions And/Or, radio button – if more than 1 condition, then;
  • all conditions have to be met before dependency can happen, select And.
  • if one of the conditions are met the dependency can happen, select Or.
  • + Add condition, add if conditions apply for this dependency transition.
    • Parameter, dropdown
    • Match, dropdown
    • Value, dropdown
• Active/Inactive slider, to activate or deactivate this dependency.

Once complete, select Save.