• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The Attachment Checkout plugin will not be ported to Confluence 2.7 or above by it's supporters. The checkout feature would help us immensely here at Univ. of Michigan Health System. I am requesting Atlassian take this feature on and incorporate it into Confluence mainstream development.

      http://confluence.atlassian.com/display/CONFEXT/Attachment+Checkout+Plugin

            [CONFSERVER-11771] Support Attachment Checkout Plugin

            Matt added a comment -

            Here's a new solution to that was released today:

            Arsenale Lockpoint is a Confluence plugin that gives your company controlled versioning of Confluence attachments, allowing locking of individual files for exclusive editing

            Learn more: http://www.arsenalesystems.com/products/arsenale-lockpoint

            Matt added a comment - Here's a new solution to that was released today: Arsenale Lockpoint is a Confluence plugin that gives your company controlled versioning of Confluence attachments, allowing locking of individual files for exclusive editing Learn more: http://www.arsenalesystems.com/products/arsenale-lockpoint

            Most recent version of "Attachment checkout plug-in" is marked as "UNSUPPORTED"

            We are planning to install this plug-in in our production environment. It seems to be risky, if some functionality won't work later after the installation. Thus, could you please advice when this plug-in would be SUPPORTED by the team? so that in future, if we face any kind of issues, we could log the ticket for resolution.

            Satish Singhsamransukh added a comment - Most recent version of "Attachment checkout plug-in" is marked as "UNSUPPORTED" We are planning to install this plug-in in our production environment. It seems to be risky, if some functionality won't work later after the installation. Thus, could you please advice when this plug-in would be SUPPORTED by the team? so that in future, if we face any kind of issues, we could log the ticket for resolution.

            AudraA added a comment -

            This plugin supports up to Confluence 3.0.2.

            And is duplicated by CONF-4462. Please comment and vote on CONF-4462 going forward.

            AudraA added a comment - This plugin supports up to Confluence 3.0.2. And is duplicated by CONF-4462 . Please comment and vote on CONF-4462 going forward.

            According to the links on the page, there IS a new version (1.0.4) in development that is compatiblity with versions newer than 2.7. Check out the compatibility matrix near the top of the page.

            Jonathan Nolen (Inactive) added a comment - According to the links on the page, there IS a new version (1.0.4) in development that is compatiblity with versions newer than 2.7. Check out the compatibility matrix near the top of the page.

            Steve - I was just changing the component to Plugin Development so that our Plugin Development department can assess the priority of this. We like to tally votes for issues like this to see their popularity. We realize not everyone who would want this knows to look here and cast their vote, but we do like to implement features that are most voted-for.

            Jeremy Largman added a comment - Steve - I was just changing the component to Plugin Development so that our Plugin Development department can assess the priority of this. We like to tally votes for issues like this to see their popularity. We realize not everyone who would want this knows to look here and cast their vote, but we do like to implement features that are most voted-for.

            Are you saying that we could decide to port the plug in ourselvers and offer support? I'm not sure I understand. I certainly don't know what's involved with that kind of committment.

            Stephen M. Gendler added a comment - Are you saying that we could decide to port the plug in ourselvers and offer support? I'm not sure I understand. I certainly don't know what's involved with that kind of committment.

            Adding 'plugin development' as a component as this could be implemented by offering support for the attachment checkout plugin.

            Jeremy Largman added a comment - Adding 'plugin development' as a component as this could be implemented by offering support for the attachment checkout plugin.

              Unassigned Unassigned
              3cbd5c2b413a Stephen M. Gendler
              Votes:
              5 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: