...
- Fields for problem start / end in edit mode (filled manually)
- Fields for problem start / end in view mode (filled automatically)
- Hiding field, that handles showing and hiding the fields above in different modes
- Validator for "Validate that Problem start is not after first outage start in Outages and that Problem end is not before last outage end in Outages "
- Post function for "Autofill Problem start (calculated) and Problem end (calculated) from Problem start and Problem end if they are filled, otherwise autofill from Outages "
Validators
Post functions
Set next action due date for Unscheduled ticket
Fields configurable.
Common use: Set empty Next action due date to the current day for issue type Unscheduled.
Set next action due date for Scheduled ticket
Fields configurable.
Common use: Auto-populate Next action due date for issue type Scheduled from Maintenance window starts if Next action due date is empty
Autofill Problem star / end
Fields configurable.
Common use: Autofill Problem start (calculated) and Problem end (calculated) from Problem start and Problem end if they are filled, otherwise autofill from Outages
Calculate the total outage
Fields configurable.
Common use: Calculate the total outage (in minutes) from custom field Outages to the custom field "Total outage"
Required fields
Set a set of fields required for a transition.
Clear fields
Clear a set of fields in this transition.
Common use: you can use transition Empty issue fields in your workflow to eq. reset issue after cloning.