Release

id (long)
Numerical digits which are considered to have larger values.

Example

234759602834500

title (string)
A text in a plain format. No rich text or new line characters allowed.

Example

ReleaseforDatabaseServerfirewallupgrades

template (release_template)
Indicates the release template used to create the release

Example

{
  "template": {
    "name": "test_template",
    "id": "105678900111042007"
  }
}

stage (release_stage)
Indicates the current stage of the release

Example

{
  "stage": {
    "name": "Submission_stage",
    "id": "100000000111042007"
  }
}

status (release_status)
Indicates the current status of the release

Example

{
  "status": {
    "name": "test_status",
    "id": "100333300111042099"
  }
}

description (html)
Contains description of the release request

Example

SuitableDescriptionoftherelease

scheduled_start_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

scheduled_end_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

created_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

completed_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

comment (string)
A text in a plain format. No rich text or new line characters allowed.

Example

Migrationapproved

next_review_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow (workflow)
Defines the complete life cycle with appropriate approvals at various stages of the release request

Example

{
  "workflow": {
    "name": "test_workflow",
    "id": "105678900111069003"
  }
}

release_requester (user)
Indicates the initiator of the release request

Example

{
  "release_requester": {
    "email_id": "test@test.com",
    "name": "test_requester",
    "id": "100000000000042013"
  }
}

release_engineer (technician)
The owner of the release request

Example

{
  "release_engineer": {
    "email_id": "test@test.com",
    "name": "test_release_engineer",
    "id": "100000000000042013"
  }
}

release_manager (technician)
User who manages the entire life cycle of the release request

Example

{
  "release_manager": {
    "email_id": "test@test.com",
    "name": "test_release_manager",
    "id": "100000000000042013"
  }
}

reason_for_release (reason_for_change)
Indicates the reasons why the release was initiated

Example

{
  "release_for_release": {
    "name": "test_reason_for_release",
    "id": "105678900111042007"
  }
}

impact (impact)
Indicates the impact of the release on business, department, group, or user

Example

{
  "impact": {
    "name": "test_impact",
    "id": "100000000111099077"
  }
}

priority (priority)
Indicates priority of the release

Example

{
  "priority": {
    "name": "test_priority",
    "id": "10033330011177799"
  }
}

category (category)
Indicates the Category of the CIs involved to this release

Example

{
  "category": {
    "name": "test_category",
    "id": "100333300111042000"
  }
}

subcategory (subcategory)
Assign the Sub Category of the selected Category

Example

{
  "subcategory": {
    "name": "test_subcategory",
    "id": "106666600111042099"
  }
}

item (item)
Indicates the item assigned to the selected Category and Sub Category.

Example

{
  "item": {
    "name": "test_item",
    "id": "100333300111042099"
  }
}

release_type (change_type)
Indicates whether it is a minor, major, significant, or standard release

Example

{
  "release_type": {
    "name": "test_release_type",
    "id": "100333300111042077"
  }
}

urgency (urgency)
Indicates the urgency of the release request

Example

{
  "urgency": {
    "name": "test-urgency",
    "id": "100670890127890"
  }
}

services (service_category)
Lists the services that might be affected due to this release

Example

{
  "services": [
    {
      "name": "test_service_1",
      "id": "122233390123003"
    },
    {
      "name": "test_service_2",
      "id": "122233390123011"
    },
    {
      "name": "test_service_3",
      "id": "122233390123015"
    }
  ]
}

assets (asset)
Indicates the assets that might be affected or involved due to this release

Example

{
  "assets": [
    {
      "name": "test-asset_1",
      "id": "234567890120999"
    },
    {
      "name": "test-asset_2",
      "id": "234567890123001"
    }
  ]
}

site (site)
Indicates the site of the release request

Example

{
  "site": {
    "name": "test_site",
    "id": "100654320111042099"
  }
}

group (group)
Indicates the assigned group of the release request

Example

{
  "group": {
    "name": "test_group",
    "id": "100333300111042099"
  }
}

risk (change_risk)
Indicates whether this involves high, low, or medium risk.

Example

{
  "risk": {
    "name": "test_risk",
    "id": "100333300111042001"
  }
}

roles (roles)
Indicates the users assigned to each release roles

Example

{
  "roles": {
    "mref_development_head": [
      {
        "id": "100000000000033531"
      }
    ],
    "mref_release_reviewer": [
      {
        "id": "100000000000042007"
      },
      {
        "id": "100000000000042019"
      }
    ],
    "mref_qa_manager": [
      {
        "id": "100000000000033531"
      }
    ]
  }
}

attachments (release_attachment)
Contains the files that are attached to the release. A Maximum of 10 attachments can be attached to a release.

Example

{
  "attachments": [
    {
      "content_type": "application/x-unknown-mime-type",
      "size": "36171",
      "file_id": "4001",
      "name": "test_file.txt"
    }
  ]
}

udf_fields (udf_fields)
Contains user defined field values associated to the release

Example

{
  "udf_fields": {
    "udf_long2": "1459402730964",
    "udf_long1": "1225",
    "udf_date1": {
      "display_value": "Feb 26, 2016 11:00 AM",
      "value": "1456464639051"
    },
    "udf_char1": "abc@test.com",
    "udf_char2": "Ned Stark"
  }
}

configuration_items (configuration_item)
Indicates Critical items for which the release request has been raised

Example

{
  "configuration_items": [
    {
      "name": "Floor 1 - Router",
      "id": "100000000000028792"
    },
    {
      "name": "Floor 12 - Router",
      "id": "100000000000028796"
    }
  ]
}

roll_out_plan (JSONObject)
Describe how the release process will be implemented

Example

{
  "roll_out_plan": {
    "roll_out_plan_description": "Rollout plan"
  }
}

roll_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

roll_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

roll_out_plan_updated_by (user)
User who last updated the roll out plan

Example

{
  "roll_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

back_out_plan (JSONObject)
Describes how the release process will proceed if the release request were to be cancelled.

Example

{
  "back_out_plan": {
    "back_out_plan_description": "Backout plan"
  }
}

back_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

back_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

back_out_plan_updated_by (user)
User who last updated the back out plan

Example

{
  "back_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

impact_details (JSONObject)
Describes how the release process will affect the business

Example

{
  "impact_details": {
    "impact_details_description": "affects user"
  }
}

impact_details_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

impact_details_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

impact_details_updated_by (user)
User who last updated the impact details

Example

{
  "impact_details_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

checklist (JSONObject)
Lists the tasks involved in the release process

Example

{
  "checklist": {
    "checklist_description": "check list"
  }
}

checklist_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

checklist_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

checklist_updated_by (user)
Indicates the user who last updated the checklist

Example

{
  "checklist_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

close_details (JSONObject)
Contains information about release closure

Example

{
  "close_details": {
    "close_details_description": "close details",
    "closure_code": {
      "name": "Closed - Cancelled",
      "id": "1791511763340999"
    }
  }
}

close_details_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

closure_code (closure_code)
Closure Code denotes the reason for closing a release request

Example

{
  "closure_code": {
    "name": "test_closure_code",
    "id": "10011139111798001"
  }
}

close_details_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

close_details_updated_by (user)
The last user who updates close details

Example

{
  "close_details_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

display_id (sequence_number)
Sequence number of the release request

Example

{
  "display_id": {
    "display_value": "RL-1",
    "value": "1"
  }
}

emergency (boolean)
Boolean value which can have two possible values. The values are true and false.

notes_present (boolean)
Boolean value which can have two possible values. The values are true and false.

deleted_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow_instance_details (workflow_instance)
Indicates the workflow execution status

Example

{
  "workflow_instance_details": {
    "id": "36338920932885067",
    "status": {
      "name": "In Progress",
      "id": "6633543434595966"
    }
  }
}

id (long)
Numerical digits which are considered to have larger values.

Example

234759602834500

title (string)
A text in a plain format. No rich text or new line characters allowed.

Example

ReleaseforDatabaseServerfirewallupgrades

template (release_template)
Indicates the release template used to create the release

Example

{
  "template": {
    "name": "test_template",
    "id": "105678900111042007"
  }
}

stage (release_stage)
Indicates the current stage of the release

Example

{
  "stage": {
    "name": "Submission_stage",
    "id": "100000000111042007"
  }
}

status (release_status)
Indicates the current status of the release

Example

{
  "status": {
    "name": "test_status",
    "id": "100333300111042099"
  }
}

description (html)
Contains description of the release request

Example

SuitableDescriptionoftherelease

scheduled_start_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

scheduled_end_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

created_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

completed_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

comment (string)
A text in a plain format. No rich text or new line characters allowed.

Example

Migrationapproved

next_review_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow (workflow)
Defines the complete life cycle with appropriate approvals at various stages of the release request

Example

{
  "workflow": {
    "name": "test_workflow",
    "id": "105678900111069003"
  }
}

release_requester (user)
Indicates the initiator of the release request

Example

{
  "release_requester": {
    "email_id": "test@test.com",
    "name": "test_requester",
    "id": "100000000000042013"
  }
}

release_engineer (technician)
The owner of the release request

Example

{
  "release_engineer": {
    "email_id": "test@test.com",
    "name": "test_release_engineer",
    "id": "100000000000042013"
  }
}

release_manager (technician)
User who manages the entire life cycle of the release request

Example

{
  "release_manager": {
    "email_id": "test@test.com",
    "name": "test_release_manager",
    "id": "100000000000042013"
  }
}

reason_for_release (reason_for_change)
Indicates the reasons why the release was initiated

Example

{
  "release_for_release": {
    "name": "test_reason_for_release",
    "id": "105678900111042007"
  }
}

impact (impact)
Indicates the impact of the release on business, department, group, or user

Example

{
  "impact": {
    "name": "test_impact",
    "id": "100000000111099077"
  }
}

priority (priority)
Indicates priority of the release

Example

{
  "priority": {
    "name": "test_priority",
    "id": "10033330011177799"
  }
}

category (category)
Indicates the Category of the CIs involved to this release

Example

{
  "category": {
    "name": "test_category",
    "id": "100333300111042000"
  }
}

subcategory (subcategory)
Assign the Sub Category of the selected Category

Example

{
  "subcategory": {
    "name": "test_subcategory",
    "id": "106666600111042099"
  }
}

item (item)
Indicates the item assigned to the selected Category and Sub Category.

Example

{
  "item": {
    "name": "test_item",
    "id": "100333300111042099"
  }
}

release_type (change_type)
Indicates whether it is a minor, major, significant, or standard release

Example

{
  "release_type": {
    "name": "test_release_type",
    "id": "100333300111042077"
  }
}

urgency (urgency)
Indicates the urgency of the release request

Example

{
  "urgency": {
    "name": "test-urgency",
    "id": "100670890127890"
  }
}

services (service_category)
Lists the services that might be affected due to this release

Example

{
  "services": [
    {
      "name": "test_service_1",
      "id": "122233390123003"
    },
    {
      "name": "test_service_2",
      "id": "122233390123011"
    },
    {
      "name": "test_service_3",
      "id": "122233390123015"
    }
  ]
}

assets (asset)
Indicates the assets that might be affected or involved due to this release

Example

{
  "assets": [
    {
      "name": "test-asset_1",
      "id": "234567890120999"
    },
    {
      "name": "test-asset_2",
      "id": "234567890123001"
    }
  ]
}

site (site)
Indicates the site of the release request

Example

{
  "site": {
    "name": "test_site",
    "id": "100654320111042099"
  }
}

group (group)
Indicates the assigned group of the release request

Example

{
  "group": {
    "name": "test_group",
    "id": "100333300111042099"
  }
}

risk (change_risk)
Indicates whether this involves high, low, or medium risk.

Example

{
  "risk": {
    "name": "test_risk",
    "id": "100333300111042001"
  }
}

roles (roles)
Indicates the users assigned to each release roles

Example

{
  "roles": {
    "mref_development_head": [
      {
        "id": "100000000000033531"
      }
    ],
    "mref_release_reviewer": [
      {
        "id": "100000000000042007"
      },
      {
        "id": "100000000000042019"
      }
    ],
    "mref_qa_manager": [
      {
        "id": "100000000000033531"
      }
    ]
  }
}

attachments (release_attachment)
Contains the files that are attached to the release. A Maximum of 10 attachments can be attached to a release.

Example

{
  "attachments": [
    {
      "content_type": "application/x-unknown-mime-type",
      "size": "36171",
      "file_id": "4001",
      "name": "test_file.txt"
    }
  ]
}

udf_fields (udf_fields)
Contains user defined field values associated to the release

Example

{
  "udf_fields": {
    "udf_long2": "1459402730964",
    "udf_long1": "1225",
    "udf_date1": {
      "display_value": "Feb 26, 2016 11:00 AM",
      "value": "1456464639051"
    },
    "udf_char1": "abc@test.com",
    "udf_char2": "Ned Stark"
  }
}

configuration_items (configuration_item)
Indicates Critical items for which the release request has been raised

Example

{
  "configuration_items": [
    {
      "name": "Floor 1 - Router",
      "id": "100000000000028792"
    },
    {
      "name": "Floor 12 - Router",
      "id": "100000000000028796"
    }
  ]
}

roll_out_plan (JSONObject)
Describe how the release process will be implemented

Example

{
  "roll_out_plan": {
    "roll_out_plan_description": "Rollout plan"
  }
}

roll_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

roll_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

roll_out_plan_updated_by (user)
User who last updated the roll out plan

Example

{
  "roll_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

back_out_plan (JSONObject)
Describes how the release process will proceed if the release request were to be cancelled.

Example

{
  "back_out_plan": {
    "back_out_plan_description": "Backout plan"
  }
}

back_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

back_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

back_out_plan_updated_by (user)
User who last updated the back out plan

Example

{
  "back_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

impact_details (JSONObject)
Describes how the release process will affect the business

Example

{
  "impact_details": {
    "impact_details_description": "affects user"
  }
}

impact_details_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

impact_details_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

impact_details_updated_by (user)
User who last updated the impact details

Example

{
  "impact_details_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

checklist (JSONObject)
Lists the tasks involved in the release process

Example

{
  "checklist": {
    "checklist_description": "check list"
  }
}

checklist_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

checklist_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

checklist_updated_by (user)
Indicates the user who last updated the checklist

Example

{
  "checklist_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

close_details (JSONObject)
Contains information about release closure

Example

{
  "close_details": {
    "close_details_description": "close details",
    "closure_code": {
      "name": "Closed - Cancelled",
      "id": "1791511763340999"
    }
  }
}

close_details_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

closure_code (closure_code)
Closure Code denotes the reason for closing a release request

Example

{
  "closure_code": {
    "name": "test_closure_code",
    "id": "10011139111798001"
  }
}

close_details_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

close_details_updated_by (user)
The last user who updates close details

Example

{
  "close_details_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

display_id (sequence_number)
Sequence number of the release request

Example

{
  "display_id": {
    "display_value": "RL-1",
    "value": "1"
  }
}

emergency (boolean)
Boolean value which can have two possible values. The values are true and false.

notes_present (boolean)
Boolean value which can have two possible values. The values are true and false.

deleted_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow_instance_details (workflow_instance)
Indicates the workflow execution status

Example

{
  "workflow_instance_details": {
    "id": "36338920932885067",
    "status": {
      "name": "In Progress",
      "id": "6633543434595966"
    }
  }
}

id (long)
Numerical digits which are considered to have larger values.

Example

234759602834500

title (string)
A text in a plain format. No rich text or new line characters allowed.

Example

ReleaseforDatabaseServerfirewallupgrades

template (release_template)
Indicates the release template used to create the release

Example

{
  "template": {
    "name": "test_template",
    "id": "105678900111042007"
  }
}

stage (release_stage)
Indicates the current stage of the release

Example

{
  "stage": {
    "name": "Submission_stage",
    "id": "100000000111042007"
  }
}

status (release_status)
Indicates the current status of the release

Example

{
  "status": {
    "name": "test_status",
    "id": "100333300111042099"
  }
}

description (html)
Contains description of the release request

Example

SuitableDescriptionoftherelease

scheduled_start_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

scheduled_end_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

created_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

completed_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

comment (string)
A text in a plain format. No rich text or new line characters allowed.

Example

Migrationapproved

next_review_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow (workflow)
Defines the complete life cycle with appropriate approvals at various stages of the release request

Example

{
  "workflow": {
    "name": "test_workflow",
    "id": "105678900111069003"
  }
}

release_requester (user)
Indicates the initiator of the release request

Example

{
  "release_requester": {
    "email_id": "test@test.com",
    "name": "test_requester",
    "id": "100000000000042013"
  }
}

release_engineer (technician)
The owner of the release request

Example

{
  "release_engineer": {
    "email_id": "test@test.com",
    "name": "test_release_engineer",
    "id": "100000000000042013"
  }
}

release_manager (technician)
User who manages the entire life cycle of the release request

Example

{
  "release_manager": {
    "email_id": "test@test.com",
    "name": "test_release_manager",
    "id": "100000000000042013"
  }
}

reason_for_release (reason_for_change)
Indicates the reasons why the release was initiated

Example

{
  "release_for_release": {
    "name": "test_reason_for_release",
    "id": "105678900111042007"
  }
}

impact (impact)
Indicates the impact of the release on business, department, group, or user

Example

{
  "impact": {
    "name": "test_impact",
    "id": "100000000111099077"
  }
}

priority (priority)
Indicates priority of the release

Example

{
  "priority": {
    "name": "test_priority",
    "id": "10033330011177799"
  }
}

category (category)
Indicates the Category of the CIs involved to this release

Example

{
  "category": {
    "name": "test_category",
    "id": "100333300111042000"
  }
}

subcategory (subcategory)
Assign the Sub Category of the selected Category

Example

{
  "subcategory": {
    "name": "test_subcategory",
    "id": "106666600111042099"
  }
}

item (item)
Indicates the item assigned to the selected Category and Sub Category.

Example

{
  "item": {
    "name": "test_item",
    "id": "100333300111042099"
  }
}

release_type (change_type)
Indicates whether it is a minor, major, significant, or standard release

Example

{
  "release_type": {
    "name": "test_release_type",
    "id": "100333300111042077"
  }
}

urgency (urgency)
Indicates the urgency of the release request

Example

{
  "urgency": {
    "name": "test-urgency",
    "id": "100670890127890"
  }
}

services (service_category)
Lists the services that might be affected due to this release

Example

{
  "services": [
    {
      "name": "test_service_1",
      "id": "122233390123003"
    },
    {
      "name": "test_service_2",
      "id": "122233390123011"
    },
    {
      "name": "test_service_3",
      "id": "122233390123015"
    }
  ]
}

assets (asset)
Indicates the assets that might be affected or involved due to this release

Example

{
  "assets": [
    {
      "name": "test-asset_1",
      "id": "234567890120999"
    },
    {
      "name": "test-asset_2",
      "id": "234567890123001"
    }
  ]
}

site (site)
Indicates the site of the release request

Example

{
  "site": {
    "name": "test_site",
    "id": "100654320111042099"
  }
}

group (group)
Indicates the assigned group of the release request

Example

{
  "group": {
    "name": "test_group",
    "id": "100333300111042099"
  }
}

risk (change_risk)
Indicates whether this involves high, low, or medium risk.

Example

{
  "risk": {
    "name": "test_risk",
    "id": "100333300111042001"
  }
}

roles (roles)
Indicates the users assigned to each release roles

Example

{
  "roles": {
    "mref_development_head": [
      {
        "id": "100000000000033531"
      }
    ],
    "mref_release_reviewer": [
      {
        "id": "100000000000042007"
      },
      {
        "id": "100000000000042019"
      }
    ],
    "mref_qa_manager": [
      {
        "id": "100000000000033531"
      }
    ]
  }
}

attachments (release_attachment)
Contains the files that are attached to the release. A Maximum of 10 attachments can be attached to a release.

Example

{
  "attachments": [
    {
      "content_type": "application/x-unknown-mime-type",
      "size": "36171",
      "file_id": "4001",
      "name": "test_file.txt"
    }
  ]
}

udf_fields (udf_fields)
Contains user defined field values associated to the release

Example

{
  "udf_fields": {
    "udf_long2": "1459402730964",
    "udf_long1": "1225",
    "udf_date1": {
      "display_value": "Feb 26, 2016 11:00 AM",
      "value": "1456464639051"
    },
    "udf_char1": "abc@test.com",
    "udf_char2": "Ned Stark"
  }
}

configuration_items (configuration_item)
Indicates Critical items for which the release request has been raised

Example

{
  "configuration_items": [
    {
      "name": "Floor 1 - Router",
      "id": "100000000000028792"
    },
    {
      "name": "Floor 12 - Router",
      "id": "100000000000028796"
    }
  ]
}

roll_out_plan (JSONObject)
Describe how the release process will be implemented

Example

{
  "roll_out_plan": {
    "roll_out_plan_description": "Rollout plan"
  }
}

roll_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

roll_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

roll_out_plan_updated_by (user)
User who last updated the roll out plan

Example

{
  "roll_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

back_out_plan (JSONObject)
Describes how the release process will proceed if the release request were to be cancelled.

Example

{
  "back_out_plan": {
    "back_out_plan_description": "Backout plan"
  }
}

back_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

back_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

back_out_plan_updated_by (user)
User who last updated the back out plan

Example

{
  "back_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

impact_details (JSONObject)
Describes how the release process will affect the business

Example

{
  "impact_details": {
    "impact_details_description": "affects user"
  }
}

impact_details_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

impact_details_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

impact_details_updated_by (user)
User who last updated the impact details

Example

{
  "impact_details_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

checklist (JSONObject)
Lists the tasks involved in the release process

Example

{
  "checklist": {
    "checklist_description": "check list"
  }
}

checklist_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

checklist_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

checklist_updated_by (user)
Indicates the user who last updated the checklist

Example

{
  "checklist_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

close_details (JSONObject)
Contains information about release closure

Example

{
  "close_details": {
    "close_details_description": "close details",
    "closure_code": {
      "name": "Closed - Cancelled",
      "id": "1791511763340999"
    }
  }
}

close_details_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

closure_code (closure_code)
Closure Code denotes the reason for closing a release request

Example

{
  "closure_code": {
    "name": "test_closure_code",
    "id": "10011139111798001"
  }
}

close_details_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

close_details_updated_by (user)
The last user who updates close details

Example

{
  "close_details_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

display_id (sequence_number)
Sequence number of the release request

Example

{
  "display_id": {
    "display_value": "RL-1",
    "value": "1"
  }
}

emergency (boolean)
Boolean value which can have two possible values. The values are true and false.

notes_present (boolean)
Boolean value which can have two possible values. The values are true and false.

deleted_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow_instance_details (workflow_instance)
Indicates the workflow execution status

Example

{
  "workflow_instance_details": {
    "id": "36338920932885067",
    "status": {
      "name": "In Progress",
      "id": "6633543434595966"
    }
  }
}

id (long)
Numerical digits which are considered to have larger values.

Example

234759602834500

title (string)
A text in a plain format. No rich text or new line characters allowed.

Example

ReleaseforDatabaseServerfirewallupgrades

template (release_template)
Indicates the release template used to create the release

Example

{
  "template": {
    "name": "test_template",
    "id": "105678900111042007"
  }
}

stage (release_stage)
Indicates the current stage of the release

Example

{
  "stage": {
    "name": "Submission_stage",
    "id": "100000000111042007"
  }
}

status (release_status)
Indicates the current status of the release

Example

{
  "status": {
    "name": "test_status",
    "id": "100333300111042099"
  }
}

description (html)
Contains description of the release request

Example

SuitableDescriptionoftherelease

scheduled_start_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

scheduled_end_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

created_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

completed_time (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

comment (string)
A text in a plain format. No rich text or new line characters allowed.

Example

Migrationapproved

next_review_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

workflow (workflow)
Defines the complete life cycle with appropriate approvals at various stages of the release request

Example

{
  "workflow": {
    "name": "test_workflow",
    "id": "105678900111069003"
  }
}

release_requester (user)
Indicates the initiator of the release request

Example

{
  "release_requester": {
    "email_id": "test@test.com",
    "name": "test_requester",
    "id": "100000000000042013"
  }
}

release_engineer (technician)
The owner of the release request

Example

{
  "release_engineer": {
    "email_id": "test@test.com",
    "name": "test_release_engineer",
    "id": "100000000000042013"
  }
}

release_manager (technician)
User who manages the entire life cycle of the release request

Example

{
  "release_manager": {
    "email_id": "test@test.com",
    "name": "test_release_manager",
    "id": "100000000000042013"
  }
}

reason_for_release (reason_for_change)
Indicates the reasons why the release was initiated

Example

{
  "release_for_release": {
    "name": "test_reason_for_release",
    "id": "105678900111042007"
  }
}

impact (impact)
Indicates the impact of the release on business, department, group, or user

Example

{
  "impact": {
    "name": "test_impact",
    "id": "100000000111099077"
  }
}

priority (priority)
Indicates priority of the release

Example

{
  "priority": {
    "name": "test_priority",
    "id": "10033330011177799"
  }
}

category (category)
Indicates the Category of the CIs involved to this release

Example

{
  "category": {
    "name": "test_category",
    "id": "100333300111042000"
  }
}

subcategory (subcategory)
Assign the Sub Category of the selected Category

Example

{
  "subcategory": {
    "name": "test_subcategory",
    "id": "106666600111042099"
  }
}

item (item)
Indicates the item assigned to the selected Category and Sub Category.

Example

{
  "item": {
    "name": "test_item",
    "id": "100333300111042099"
  }
}

release_type (change_type)
Indicates whether it is a minor, major, significant, or standard release

Example

{
  "release_type": {
    "name": "test_release_type",
    "id": "100333300111042077"
  }
}

urgency (urgency)
Indicates the urgency of the release request

Example

{
  "urgency": {
    "name": "test-urgency",
    "id": "100670890127890"
  }
}

services (service_category)
Lists the services that might be affected due to this release

Example

{
  "services": [
    {
      "name": "test_service_1",
      "id": "122233390123003"
    },
    {
      "name": "test_service_2",
      "id": "122233390123011"
    },
    {
      "name": "test_service_3",
      "id": "122233390123015"
    }
  ]
}

assets (asset)
Indicates the assets that might be affected or involved due to this release

Example

{
  "assets": [
    {
      "name": "test-asset_1",
      "id": "234567890120999"
    },
    {
      "name": "test-asset_2",
      "id": "234567890123001"
    }
  ]
}

site (site)
Indicates the site of the release request

Example

{
  "site": {
    "name": "test_site",
    "id": "100654320111042099"
  }
}

group (group)
Indicates the assigned group of the release request

Example

{
  "group": {
    "name": "test_group",
    "id": "100333300111042099"
  }
}

risk (change_risk)
Indicates whether this involves high, low, or medium risk.

Example

{
  "risk": {
    "name": "test_risk",
    "id": "100333300111042001"
  }
}

roles (roles)
Indicates the users assigned to each release roles

Example

{
  "roles": {
    "mref_development_head": [
      {
        "id": "100000000000033531"
      }
    ],
    "mref_release_reviewer": [
      {
        "id": "100000000000042007"
      },
      {
        "id": "100000000000042019"
      }
    ],
    "mref_qa_manager": [
      {
        "id": "100000000000033531"
      }
    ]
  }
}

attachments (release_attachment)
Contains the files that are attached to the release. A Maximum of 10 attachments can be attached to a release.

Example

{
  "attachments": [
    {
      "content_type": "application/x-unknown-mime-type",
      "size": "36171",
      "file_id": "4001",
      "name": "test_file.txt"
    }
  ]
}

udf_fields (udf_fields)
Contains user defined field values associated to the release

Example

{
  "udf_fields": {
    "udf_long2": "1459402730964",
    "udf_long1": "1225",
    "udf_date1": {
      "display_value": "Feb 26, 2016 11:00 AM",
      "value": "1456464639051"
    },
    "udf_char1": "abc@test.com",
    "udf_char2": "Ned Stark"
  }
}

configuration_items (configuration_item)
Indicates Critical items for which the release request has been raised

Example

{
  "configuration_items": [
    {
      "name": "Floor 1 - Router",
      "id": "100000000000028792"
    },
    {
      "name": "Floor 12 - Router",
      "id": "100000000000028796"
    }
  ]
}

roll_out_plan (JSONObject)
Describe how the release process will be implemented

Example

{
  "roll_out_plan": {
    "roll_out_plan_description": "Rollout plan"
  }
}

roll_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

roll_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

roll_out_plan_updated_by (user)
User who last updated the roll out plan

Example

{
  "roll_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

back_out_plan (JSONObject)
Describes how the release process will proceed if the release request were to be cancelled.

Example

{
  "back_out_plan": {
    "back_out_plan_description": "Backout plan"
  }
}

back_out_plan_description (html)
HTML is a text area where html elements can be used.

Example

<b>The content to be displayed</b>

back_out_plan_updated_on (datetime)
Represents a date/time as a JSON Object. Would contain the value and the display_value attributes.

value : The time in long format (No. of milliseconds from Jan 1, 1970 ).

display_value : The time in a readable form in a format as personalized by the user. If not personalized, default format would be used.

back_out_plan_updated_by (user)
User who last updated the back out plan

Example

{
  "back_out_plan_updated_by": {
    "email_id": "test@test.com",
    "name": "test_user",
    "id": "100000000000042013"
  }
}

impact_details (JSONObject)
Describes how the release process will affect the business

Example

{
  "impact_details": {
    "impact_details_description": "affects user"
  }
}