in forge manifest for smart link team work graph , you can’t put atlassian.net only in domains ?
atlassian.net , https://*.atlassian.net and *.atlassian.net didnt work for me it only worked when i put MyInstance.atlassian.net
graph:smartLink:
- key: jira-smartlink
icon: resource:icons;cov-jct.svg
name: Jira Issue Smart Link
function: getEntityByUrlFn
domains:
- atlassian.net
subdomains: true
patterns:
- ^https:\/\/[\w-]+\.atlassian\.net\/browse\/([A-Z][A-Z0-9]+-\d+)$
any idea on how would i allow it for any instance where the app is installed ?
1 Like
Hi @HaithemGhattas1 ,
Great question. I will check with the team, but I believe Smart Links are only supporting external sites as we have our own Internal Smart Links for atlassian.net domain. In these instances our Smart Link resolvers will take priority.
Regards
Eugene
1 Like
Hi @EugeneSmal
This is a useful feature for Marketplace Apps which generate new content, to be able to provide additional context for the links to the generated content.
At some point, we will also be looking at feeding / associating the generated content to the team work graph via connector.
I could be wrong, but if the Smart Link feature is only available for external sites, it would not be best the user experience for the data fed via existing marketplace apps.
Can the SmartLink feature can be opened for atlassian.net domain with some mechanism for restricting the processing to the path specific to the app. I would be happy to elaborate on our use case if required.
1 Like