Actually, other apps can listen to other apps.

In my case if my bot post a Github link, the Github app unfurled the link, so I think is really a problem with the JiraCloud app.

I found this ticket and I know it's old but I wanted to post for two reasons:

1. To state that this broke my heart
2. Offer a workaround

Workaround:   I set my automation (which uses the Slack webhook) that posts "Message text ticket: XYZ-1243 . More text here"  to make the ticket XYZ-1243 into a link using smart values like so: 

"Message text  <{{issue.url}}|{{issue.key}} - {{issue.summary}}>. More text here" 

edit: this editor ate my curly mustaches!

Hi cgriego unfortunately, I'm going to have to close this as it is not possible for any Slack app to listen to other Slack apps (as it is a limitation of the Slack API). I definitely get the use case! We will continue to relay this to Slack as a platform feature request.

Hi, it was my support ticket that prompted this feature request. To add some background, while I totally understand the default behavior, my team is using Geekbot which is used for asynchronous standups in Slack. Team members give their status to the app/bot user and then it broadcasts that into channels. Those messages in the broadcast channels are posted as the user (not as the Geekbot bot/user), but are still flagged as being posted by an app (showing APP in a gray box next to the user's name/avatar). When issue keys are referenced in these statuses, we want them unfurled and to have the Jira bot/user post the expanded issue preview but it is not.