Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Using OneDrive, Dropbox, Google Drive, etc as file repository in Confluence

The new editor has killed our information management strategy.  Most of our information is maintained in Confluence pages.  But when we had a file (supplier RFQ, design spec, etc) - we used file list pages to organize the files by project and then linked to the file from any page that needed it.  This is how we maintained a single point of truth for our documentation.

In the new editor - the only way to link a file to a page is to upload the file to the page.  This completely eliminates our ability to maintain a single point of truth and make sure we reference the document everywhere needed.

I'm wondering if anyone has experience using other services (OneDrive, Dropbox, Google Drive, Sharepoint) for file storage and integrating with Confluence.  Any recommendations if any services work better than others?

If I can't solve this problem, I'm going to have to move to a new tool and just keep Confluence until the current information in there ages out.

2 answers

0 votes
Diego Atlassian Team Jan 09, 2020

Hello there! Thanks for reaching out @Jeannine Hooper-Yan .

The latest updates to our editor did bring a lot of changes! One of them is that we can no longer link to attachments. Here is a report on that:

However, I believe that you can try and keep a pretty similar workflow even with such limitations. We can use a combination of labeling and the Attachments macro.

You can check how labels work here:

 

And here is our documentation on the Attachments Macro:

What we need to do is this:

  1. Label our attachments
  2. Create our page
  3. Add the Attachments Macro
  4. Enter the macro´s settings
  5. Set the page into which the macro should look into
  6. Limit the results by using Filename Patterns, Labels and sorting

 

I understand that this solution is not ideal or elegant or fast as linking to attachments, but I believe it achieves a similar result. Let me know if this workaround helps you out, Jeannine!

Looking forward to your reply.

Hi Jeannine,

You can have a look to this app, Team Files, it support live files attach to Confluence for a single source of truth. It’s also available for Jira.

It supports attaching files from Dropbox, Google Drive, SharePoint, OneDrive, Box, Egnyte and even FTP servers

Check here:

https://marketplace.atlassian.com/1216862

 

Hope it helps

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

Confluence Bingo Round 3!

That’s right! Grandma’s back at it again, and this time she’s brought all her friends. In honor of Team '21, this Bingo round is dedicated to all things team-related, and the prizes are no exception....

2,200 views 30 21
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you