Maybe @daniel can confirm, but I thought Web Fragment Finder was quite comprehensive so maybe atl.footer was introduced after Web Fragment Finder was last updated?
In any case, if atl.footer is showing in all places except for one, then it seems like a bug. I’ll try reaching out to the JSD team.
A separate footer extension point exists for knowledgebase articles to avoid accidentally exposing app content to customers that should not be visible to them. This extension point is documented in https://developer.atlassian.com/cloud/jira/service-desk/customer-portal/#footer-panel. If your app’s iframe you use for the atl.footer extension point doesn’t expose data that shouldn’t be visible to the portal customers of our JSD customers, then you can declare this extension point pointing to the same URL you use for the atl.footer extension point.
Firstly, it’s probably best not to change posts too much because responses to the posts will make less sense and it will be difficult for others to follow the topic when they come across it.
My understanding of the changes is that in your experience, neither the atl.footer nor the serviceDeskPortalFooter are visible in JSD Cloud knowledgebase articles. Is that right?
No worries - thats why I added the note at the bottom of the question - so that the responses still make sense. You are correct neither are visible for knowledgebase articles
Thanks @david,
I changed the issue type from suggestion to bug since as you point out, the behaviour is inconsistent with the documentation.
Regards,
Dugald
