Work Items can be customized from the main Administration page to better fit your business needs. Navigate to the main work item screen and find the Administration section in the table header. Work item types, statuses, and fields will be configurable there.
Table of Contents |
---|
minLevel | 1 |
---|
maxLevel | 6 |
---|
outline | false |
---|
type | list |
---|
printable | false |
---|
|
...
Work Item Types
Work item type is a container for the work item. You can use types to group your work items together in a way that makes sense for your team or company. By default, FlexDeploy will come with “Feature”, “Bug”, “Debt”, and “Risk” types out of the box. You can choose to use to keep using those types or scrap them and create your own.
...
Property Name | Required | Description |
---|
Code | Yes | Work item field code. Uniquely identifies the field. |
Display Name | No | Work item display name. |
Description | No | Work item description. |
Work Item Types | Yes | The work item types this field will apply to. In other words, if a field is assigned the “Feature” Work Item Type, then all Work Items of type “Feature” will display that field. One or more Work Item Types can be set. |
Field Group | Yes | Work item field group. The group which contains the current field. The field group name will appear as a section on the work item. |
Field Data Type | Yes | Work item field data type sets the visual format of the field on UI along with simple validation. For more complex validation see “Validation Script”. The following data types are supported: Text Field Text Area Number - UI validation will only allow integers / whole numbers Decimal - UI validation will allow both integers and floating point numbers Checkbox - True / False boolean field Duration - Duration is the measure of time. Ui validation will only allow unit of measure formats. I.E. +2d or -3w Date - UI validation expects mm/dd/yyyy format DateTime - UI validation expects mm/dd/yyyy hh:mm am/pm. The date time is selectable from a calendar for ease of use. URL - UI validation expects a valid URL JBDCURL - UI validation expects a valid JDBC URL. See packageDeploy (JDBC) for examples of valid JBDC url. Directory User Select (Username or User Id) - UI provides a selection from FlexDeploy users. Value passed to the work item can be username or user id. Group Select (Group name or Group ID) - UI provides a selection from FlexDeploy groups. Value passed to the work item can be name or id.
Example of how each input would display on the work item |
Definition Script | No | Work item definition script. This is a groovy script to set various values like defaults or basic validations. |
List Data Script | No | Work item list data script. This is a groovy script which defines a set of options the user can choose from for this fields value. List Data Script will only apply to String based fields i.e. TextField and not DateTime. The script is expecting one of 3 return types: Code Block |
---|
// An array of values
return ["PROD", "NON-PROD"]
// A comma separated string
return "Break Fix,Enhancement,Problem,Project,request,Risk remediation"
// An array of ListValueDataObject
// Use the constructor or setters on the ListValueDataObject objects to set appropriate values
return [new ListValueDataObject("value1"), new ListValueDataObject("label2", "value2"), new ListValueDataObject("label3", "value3", "Description")]
////////////////////////////////////////////////////////////////////////////////////
// ListValueDataObject has the following variables
private String mLabel;
private String mValue;
private String mDescription;
// ListValueDataObject has the following constructors
public ListValueDataObject()
{
super();
}
public ListValueDataObject(String pLabel, String pValue, String pDescription)
{
mLabel = pLabel;
mValue = pValue;
mDescription = pDescription;
}
public ListValueDataObject(String pLabel, String pValue)
{
mLabel = pLabel;
mValue = pValue;
}
public ListValueDataObject(String pValue)
{
mLabel = pValue;
mValue = pValue;
}
// ListValueDataObject has the following methods
public void setLabel(String pLabel)
{
this.mLabel = pLabel;
}
public String getLabel()
{
return mLabel;
}
public void setValue(String pValue)
{
this.mValue = pValue;
}
public String getValue()
{
return mValue;
}
public void setDescription(String pDescription)
{
this.mDescription = pDescription;
}
public String getDescription()
{
return mDescription;
} |
|
Validation Script | No | Work item validation script. This is a groovy script allowing for more complex validations beyond simple UI validations like isRequired or min/max value. Example Date based Validation script: Code Block |
---|
| // Validation script must return or true or false
// ValidationMessage is a variable specific to this script which will be display on the UI if this script returns false
if (form.PLANNEDSTART != null && form.PLANNEDEND != null) {
if (form.PLANNEDEND.before(form.PLANNEDSTART)) {
ValidationMessage = "Planned end date is not before start date "
return false
}
}
return true |
This script is executed when the status of a work item is changed. Status change will not go through if the validation script fails. |
Field Script Objects and Variables
...