Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-68620

Can't access attached files on the new editor

XMLWordPrintable

      Issue Summary

      Using the new editor, it's not possible to access the attached files using the "Files & Images" button. Accessing "recent uploads" is not the same as accessing files from existing attachments on the page as it uploads a new version of a file.

      Steps to Reproduce

      1. Create a page
      2. Click on the "Files & Images" button.
      3. Attach a file
      4. Edit the page and click on the "Files & Images" button to re-attach the file inserted in Step 3

      Expected Results

      • It should be possible to access the attached files using the "Files & Images" button.

      Actual Results

      • Accessing attached files using the "Files & Images" button will only give you an option to "recent uploads" which is not the same as accessing files from existing attachments on the page as it uploads a new version of a file.

      Note

      Using the ! to fetch a file from the attachments page in the old editor will create a reference to other pages. This feature is not possible using the "Files & Images" button in the new editor.

      Workaround

      There is no known workaround for this behavior. A workaround will be added here when available

            [CONFCLOUD-68620] Can't access attached files on the new editor

            Pinned comments

            Pinned by Roberto M.

            Owen Wallis added a comment -

            Hi, I am the Product manager responsible for this area.

            Looks like there are 3 JAC tickets all covering the same problem space:

            https://jira.atlassian.com/browse/CONFCLOUD-68620

            https://jira.atlassian.com/browse/CONFCLOUD-68852

            https://jira.atlassian.com/browse/CONFCLOUD-65344

            I'm aware the need here is to be able to attach files already uploaded into Confluence. With the main use case being single source editing (i.e. change a logo in one place and all other logos update).

            While my team is not actively working on this area right now I wanted to reassure you I'm watching all 3 tickets and read every comment. 

            Owen Wallis added a comment - Hi, I am the Product manager responsible for this area. Looks like there are 3 JAC tickets all covering the same problem space: https://jira.atlassian.com/browse/CONFCLOUD-68620 https://jira.atlassian.com/browse/CONFCLOUD-68852 https://jira.atlassian.com/browse/CONFCLOUD-65344 I'm aware the need here is to be able to attach files already uploaded into Confluence. With the main use case being single source editing (i.e. change a logo in one place and all other logos update). While my team is not actively working on this area right now I wanted to reassure you I'm watching all 3 tickets and read every comment. 

            All comments

            Joseph Orellana added a comment -

            This issue needs to be reopened. This issue has not been fixed.

            Joseph Orellana added a comment - This issue needs to be reopened. This issue has not been fixed.

            Jan Bunse added a comment -

            How can this issue be "closed" and "fixed"? It is not, it is not even "minor", because it impacts productivity A LOT.

            Sorry, but this is unacceptable.

            Jan Bunse added a comment - How can this issue be "closed" and "fixed"? It is not, it is not even "minor", because it impacts productivity A LOT. Sorry, but this is unacceptable.

            Kirstin Seidel-Gebert added a comment -

            Same here. How can we add attached images inside the new editor? Please explain!

            Kirstin Seidel-Gebert added a comment - Same here. How can we add attached images inside the new editor? Please explain!

            Martin Sauter added a comment - - edited

            @Yuan Zhuang Can you please explain in what way this issue is «fixed» as it says under «resolution»?

            As far as I can see in my Confluence instance, this problem is still present.

            Martin Sauter added a comment - - edited @Yuan Zhuang Can you please explain in what way this issue is «fixed» as it says under «resolution»? As far as I can see in my Confluence instance, this problem is still present.

            Paul Fleer added a comment -

            This seems to be a basic user experience workflow that should have been pretty quick to identify in testing. Very disappointing to see it was removed.

            Paul Fleer added a comment - This seems to be a basic user experience workflow that should have been pretty quick to identify in testing. Very disappointing to see it was removed.

            Jan Bunse added a comment -

            After migrating to confluence cloud, we just discovered this feature is missing. I kindly (and urgently) ask you to again add a popup to choose files from the attachments. Thank you!

            Jan Bunse added a comment - After migrating to confluence cloud, we just discovered this feature is missing. I kindly (and urgently) ask you to again add a popup to choose files from the attachments. Thank you!

            Martin Cleaver added a comment -

            All the community can do is vote and hope that the next time the editor is touched Atlassian will get this processed from the backlog.

            It is rather odd to have something that has always worked just disappear for more than a year. Why upload an attachment already listed just to embed it? It is counterintuitive and a plainly bad user experience.

            Having three tickets open is a little weird too as it leaves the community to wonder whether it is appropriate to vote on all of them, and leaves Atlassian's product team about whether we did.

            Thanks,

               Martin Cleaver.

             

            Martin Cleaver added a comment - All the community can do is vote and hope that the next time the editor is touched Atlassian will get this processed from the backlog. It is rather odd to have something that has always worked just disappear for more than a year. Why upload an attachment already listed just to embed it? It is counterintuitive and a plainly bad user experience. Having three tickets open is a little weird too as it leaves the community to wonder whether it is appropriate to vote on all of them, and leaves Atlassian's product team about whether we did. Thanks,    Martin Cleaver.  

            Pinned by Roberto M.

            Owen Wallis added a comment -

            Hi, I am the Product manager responsible for this area.

            Looks like there are 3 JAC tickets all covering the same problem space:

            https://jira.atlassian.com/browse/CONFCLOUD-68620

            https://jira.atlassian.com/browse/CONFCLOUD-68852

            https://jira.atlassian.com/browse/CONFCLOUD-65344

            I'm aware the need here is to be able to attach files already uploaded into Confluence. With the main use case being single source editing (i.e. change a logo in one place and all other logos update).

            While my team is not actively working on this area right now I wanted to reassure you I'm watching all 3 tickets and read every comment. 

            Owen Wallis added a comment - Hi, I am the Product manager responsible for this area. Looks like there are 3 JAC tickets all covering the same problem space: https://jira.atlassian.com/browse/CONFCLOUD-68620 https://jira.atlassian.com/browse/CONFCLOUD-68852 https://jira.atlassian.com/browse/CONFCLOUD-65344 I'm aware the need here is to be able to attach files already uploaded into Confluence. With the main use case being single source editing (i.e. change a logo in one place and all other logos update). While my team is not actively working on this area right now I wanted to reassure you I'm watching all 3 tickets and read every comment. 

            mawi added a comment -

            This has been closed as a duplicate. Unfortunately all votes for this issue are "lost", the open issue has much less votes.

            Classic move

            PO rule: Always move to the newer work item that has less visibility. If there is an annoying request that has as alot of attention, create a new one, close the original one as a duplicate. Voila! Less attention to the annoying problem. ;-P 

            mawi added a comment - This has been closed as a duplicate. Unfortunately all votes for this issue are "lost", the open issue has much less votes. Classic move PO rule: Always move to the newer work item that has less visibility. If there is an annoying request that has as alot of attention, create a new one, close the original one as a duplicate. Voila! Less attention to the annoying problem. ;-P 

            T H added a comment -

            This has been closed as a duplicate. Unfortunately all votes for this issue are "lost", the open issue has much less votes.

            So all watchers: Please vote for https://jira.atlassian.com/browse/CONFCLOUD-68852 !

            T H added a comment - This has been closed as a duplicate. Unfortunately all votes for this issue are "lost", the open issue has much less votes. So all watchers: Please vote for https://jira.atlassian.com/browse/CONFCLOUD-68852 !

              441e7ea28a31 Yuan Zhuang
              jalor Janice Alor (Inactive)
              Affected customers:
              58 This affects my team
              Watchers:
              75 Start watching this issue

                Created:
                Updated:
                Resolved: