-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
3
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Currently the versions of a page do not reflect the included version of attachments in the page. When looking at older version of a page, attachment are always referenced as latest version.
Request:
When including or linking an attachment in a page the version of the attachment should be referenced in the page. As soon as a newer version of an attachment is added, the version of the page should also reflect this.
This enables workflows to easily work for attachment approvals. It might also help enterprise customers to move from classic document-management (e.g. Sharepoint) to a compliant web-based document-control, not only referring an approved office document within a page, but the complete confluence page as compliant document.
- relates to
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Under Consideration
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-37156] Link attachment modifications to page history
+1 The page version should reflect all page-related changes, including new or changed attachments.
Same here. We'd like to use Confluence for our QMS and design documents, but it is impossible to view consistent historical baselines due to this issue.
It should not be too hard to implement either: Attachment history is already recorded along with the timestamp when an attachment was updated. When viewing the page history, just render the most recent version of each attachment at the time the page version was created. That already gives you 95% of the benefits. To get to 100%, just bump the page version every time an attachment changes.
Working in a big Automotive industry company - we'd definitely need this functionality for the reasons already mentioned above (Document/Configuration Management!)
Same here: we really miss this feature! Many pages contain documents that cannot be created as wiki-pages.
We use Comala Workflows for the publishing of documents and in this environment it is even more important.
+1 from Continental
It is only right that a page reflects attachment versions relating to the current version. It's clearly not the case right now - page v1 displaying attachments from the latest version e.g. v999?
This unnatural behavior is a showstopper for all considering Confluence for version and configuration management.
In reviewing the Issue links to other similar issues it appears these are more or less all the same topic in one or more forms.
I would place a vote that this topic is bigger than it appears and spans several of the issues that have been open therefore making it more widespread and a larger issue to consider resolving. I will spare myself from placing comments on all of the other issues, but I think the point is being made.
Thanks,
Melody
I added comments to two pages regarding this topic. I vote yes!!!
https://community.atlassian.com/t5/Confluence-discussions/Would-love-some-feedback-on-using-content-collaboration-tools/m-p/707377#M1177
https://community.atlassian.com/t5/Life-Sciences-discussions/Latest-Version-of-Image-displaye-in-a-Previous-Version-of-a/m-p/699304#M54
This is what I had to do to view the images: Open the Preview - top left corner of the window: select a version from the drop down arrow - top right window: select download from the download option and download the image file to a viewer or save it; whether you are in the list of attachments attempting to view the historical image versions or in the file list. If you can image a single page with more than 47 images all with 10 or more versions....
I am glad to be able to contribute some more information on this.
Thanks,
Melody
+1
this functionality is required for document and configuration management