The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
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?
2 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
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":
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.