For managing the Golive Global Settings, click on the “Global Settings” menu entry:
You must be Jira or Apwide Administrator to update the Golive Global Settings More information: Security & Permissions
In the “Jira Projects” tab, you can map Golive Applications to your Jira Projects.
More information: Jira Projects Mapping
In the “Security” tab, you can change the XSS Sanitization Mode. This option gives you the possibility to select which sanitization you want apply on HTML fields such as attribute values.
“Validation” and “Explicit Sanitization” will block users from saving invalid content, asking them to correct it. If sanitization was disabled during a period of time and invalid content is stored, “Validation” will display invalid content as-is, while “Explicit Sanitization” will sanitize the content before displaying it.
“Silent Sanitization” will always clean what users save, without notification.
“No XSS protection” will completely disable XSS protection and it will expose you to XSS attack!
You can find more information about Cross Site Scripting (XSS) on OWASP website.
By default, the Golive menu displayed in the Jira navigation bar is labelled "Golive". In the “Preferences” tab, you can change this label. For instance, you can name it “Environments”.
If no time information is provided, the time of a Start Date will always be set at the beginning of the day and the time of an End Date will always be set at the end of the day. This means that an Event starting and finishing on the same date will have a duration of 1 day (recommended settings).
if no time information is provided, the time of both Start and End Date will be set at the beginning of the day. This means that an Event starting and finishing on the same date will have no duration and will be considered as a milestone (default behaviour before Golive 8.5)