2023-02-09
Version 9.8 released on February 9th, 2023 Golive Marketplace Listing | Version History
Improvements
New Environment Custom Field Options
Choose precisely which environments should be suggested on a per custom field configuration. Possibility to show and filter environments not mapped to any projects
Learn moreEnvironment Custom Field Differential Update Rest API
Possibility to use ADD/REMOVE in addition to SET operation when updating custom field values through Jira Issue Update Rest APINew Option to Show/Hide Environment Issue Panel Only
Display option of environment issue panel is not anymore linked to the display of project page. You can choose to show/hide each of them independentlyNew Capabilities for Status Change Monitoring API
Possibility to use a conversion table to map an external monitoring tool specific status with Golive internal status. Possibility to avoid updating environments in some specific statuses when a status change is triggeredNew Application Version Mapping Option
The possibility to disable application version mapping and configuration dialog has been improved
Learn more
Fixed Bugs
Wizard: not able to create environment when not having permission on default secured attributes.
Automation: missing pieces of information about environment not available in message payloads due to undesired permission check.
Highlights
New Environment Custom Field Options
You don’t anymore to mapping Project and Application together for filtering environments custom field options. You can completely customize which suggestions should be made on a per custom field basis:
Environment Custom Field Differential Update Rest API
Update Environments custom field values by adding or removing value(s) without modifying all the existing entries.
Example of call to http://${jiraBaseUrl}/issue/${issueId}:
{
"update": {
"customfield_10000": [{
"add": ["101"]
}],
"customfield_10001": [{
"remove": ["2"]
}]
}
}
New Option to Show/Hide Environment Issue Panel Only
You want to use only one of the Golive Project Page or Environments Issue Panel. Display configuration has been split and you can choose which one to choose, globally, or on a per project basis.
New Capabilities for Status Change Monitoring API
If your monitoring tool provide limited capabilities in terms of webhook customization, you can now provide status mapping directly in the messages exchanged with Golive. For example, monitoring use “Ok” and “Not Ok” to represent “Up”/”Down” status. Let’s configure this mapping in the payload of your call:
{
"scope": {
"criteria": [
{
"name": "Country",
"values": ["US"]
}
]
},
"status": {
"name": "Ok"
},
"statusMapping": {
"Ok": { "name": "Up" },
"Not Ok": { "name": "Down" }
}
}
Or, Golive received a status change notification, but you don’t want to update environments currently in specific status, for example “In Maintenance”. You can specific a list of status to ignore:
{
"scope": {
"criteria": [
{
"name": "Country",
"values": ["US"]
}
]
},
"ignoredStatuses": [
{ "name": "In Maintenance" }
],
"status": {
"name": "Down"
}
}
Have a look at the other integration scenarios such as New Relic, Datadog, Dynatrace…