-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Atlassian Update - 08 June 2022
Hi everyone! We're happy to announce that we have deployed the following fixes for OneDrive and Sharepoint links:
- We now support smart links for links shared via "Share with people with existing access” and "Share with specific people"
- We now support embeds for PDF and CSV links
Andre | Product Manager, Linking Platform
Issue Summary
Convert all types of SharePoint links to smartcards
Steps to Reproduce
- As of now, only the links created with the "Anyone with the Link" can be converted to Smart Links. All the other mentioned options are not working.
- Open the page in Microsoft Share and go to Link Settings
- Select any option (other than 'Anyone with the Link') and paste it on the confluence page
Expected Results
All the SharePoint generated links should get converted to SmartCards:
Support for the following types of share links:
- People within the instance
- People with existing access
- Specific people
Actual Results
Not all the SharePoint-generated links get converted to SmartCards.
Workaround
Open the target document in the browser, copy the URL from the address bar and paste that into the Confluence page
- is related to
-
CONFCLOUD-73899 Smart Links does not display embed option after pasting Microsoft OneDrive/SharePoint links
- Gathering Interest
Hi c124c5bdcbf1, thank you for your reply. It appears to me that Atlassian took on the task of replacing & upgrading the existing functionality already offered by the addon, but appear to have failed to take into consideration handling of HTML links generated by Microsoft's Share > Copy link function, which to me seems like the most common user journey (I believe more users will use Share>Copy than simply copy URL from the address bar, but I'm not 100% sure). It also seems to me that Atlassian released the substitute solution and deprecated the original addon solution without verifying that the new solution achieves all the features/objectives offered by the original addon solution, else the shortfalls like this one would have been documented somewhere, which appears to be not the case. As you pointed out the old solution could handle any type of link while the new one fails to handle the most frequently used HTML link type that it generated by Microsoft's Share > Copy link function. Given that we are talking about solution substitution and failure to handle most common use case (Share > Copy link) I still see it this as a bug/regression and ask that it be recorded as such rather than a task to look into this. Also I would like to add that while I do value the widening of the scope of link conversion to other apps/functions, I don't feel that this should be justification for silently axing excising functionality like the handling of HTML links, without even a mention to end users. I would also like to draw attention to the summary of this bug Convert all types of SharePoint / One Drive links to smartcards which has been marked Closed despite the fact that the solution is still not converting all types of SharePoint / OneDrive links and in actual fact fails to handle the most common HTML links generated by Microsoft's Share > Copy link function. Given that the bug objective/ expected results of this bug still fail, I would request that this bug be reopened.