added a list of ITSM manifest variables (#2837)

Author: benPearce1

src/pages/docs/approvals/jira-service-management/index.md

@@ -241,6 +241,22 @@ The following list assumes the linked change is in an **approved** state.
 
 **If at any time a `Planned end` is exceeded and the linked change request is not approved, the deployment will be terminated.**
 
+## Available Variables in a Deployment or Runbook
+
+:::div{.info}
+The following variables are only available in version 2025.4 and later
+:::
+
+| Variable | Notes |
+|--|--|
+| `Octopus.JiraServiceManagement.ChangeRequest.Number` | The number of the matched or created change request | 
+| `Octopus.JiraServiceManagement.ChangeRequest.Id` | The system identifier of the matched or created change request |
+| `Octopus.JiraServiceManagement.Connection.Id` |  |
+| `Octopus.JiraServiceManagement.Connection.Name` | |
+| `Octopus.JiraServiceManagement.Connection.BaseUrl` | |
+| `Octopus.JiraServiceManagement.Connection.Username` | |
+| `Octopus.JiraServiceManagement.Connection.Token` | |
+
 ## Known issues and limitations
 
 - Once an Issue is deemed to be related to a deployment, then only this Issue will be evaluated for 

src/pages/docs/approvals/servicenow/index.md

@@ -273,7 +273,6 @@ The expected ServiceNow value doesn't always align with the displayed value. In
 
 For a full list of available fields and values refer to the [ServiceNow docs](https://developer.servicenow.com/dev.do#!/reference/api/utah/rest/change-management-api).
 
-
 ### Respecting change windows
 
 :::div{.warning}
@@ -293,6 +292,24 @@ The following list assumes the linked change is in an **approved** state.
 
 **If at any time a `Planned end date` is exceeded and the linked change request is not approved, the deployment will be terminated.**
 
+## Available Variables in a Deployment or Runbook
+
+:::div{.info}
+The following variables are only available in version 2025.4 and later
+:::
+
+| Variable | Notes |
+|--|--|
+| `Octopus.ServiceNow.ChangeRequest.Number` | The number of the matched or created change request | 
+| `Octopus.ServiceNow.ChangeRequest.SysId` | The system identifier of the matched or created change request |
+| `Octopus.ServiceNow.Connection.Id` |  |
+| `Octopus.ServiceNow.Connection.Name` | |
+| `Octopus.ServiceNow.Connection.BaseUrl` | |
+| `Octopus.ServiceNow.Connection.OAuthClientId` | |
+| `Octopus.ServiceNow.Connection.OAuthClientSecret` | |
+| `Octopus.ServiceNow.Connection.Username` | |
+| `Octopus.ServiceNow.Connection.Password` | |
+
 ## Known Issues and limitations
 
 - Once a CR is deemed to be related to a deployment, then only this CR will be evaluated for the deployment to proceed. If the CR is incorrect, you will need to cancel the deployment, close the CR and try the deployment again.