Linked Issues in Services Object not appearing

[Angelbert Palad]

When creating an incident for a service by populating the 'Affected Services' field, the issue or ticket does not show in the 'Linked Issues' section of the Services object.

Thus I cannot make the AQL connectedTickets() work for my automation.

Any idea?

[Daniel Kerr]

I've just run into this issue as well, and after some searching, I noticed that this seems to be a missed requirement from Atlassian. See the below suggestion that is "Under consideration":

https://jira.atlassian.com/browse/JSDCLOUD-10435

If anyone has a workaround to this, I'd love to know. My only suggestion for a workaround is that you build out your own services object type in your own object schema and create a custom field such as "Impacted Services" to understand linked issues for a particular service (object) when in the object schema.

[Scott Bickerton]

Are your incidents open (unresolved) when you are looking at the Services object?