Merge pull request #2354 from OctopusDeploy/finnd-JSM-tasklogs

updated JSM to mention output to server logs instead of tasklogs

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

@@ -168,11 +168,9 @@ closed the above process will be followed again.
 
 Once an Issue has been found, the deployment will only proceed if the **State** of the CR is 
 `Implementing`. If the **State** is either `Preview`, `Planning`, `Authorize`, or `Awaiting 
-Implementation` the 
-deployment will wait. Any other **State** will cause the deployment task to fail.
+Implementation` the deployment will wait. Any other **State** will cause the deployment task to fail. For deployments using Highly Available (HA) Octopus, the logs will be written to the server logs instead of the task logs.
 
 :::div{.info}
-
 The only supported states are those defined in the default Issue lifecycle
 :::