• 6
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      It would be neat if, when viewing the page history, you could see an "annotated" view, ala FishEye, to see who edited each line/section of the page and when. When viewing long documents with multiple collaborators, it's quite hard to go through the page history in order to find out who edited a particular sectionn last, which this improvement would help with.

            [CONFCLOUD-5884] Page history should have "annotated" view

            Mike Fair added a comment -

            This is a much needed feature.   Without high quality editing tools, the collaborative process using Atlassian tools cannot work effectively.

            Mike Fair added a comment - This is a much needed feature.   Without high quality editing tools, the collaborative process using Atlassian tools cannot work effectively.

            We're coming up on this ticket's 18th birthday.  It'll be old enough to vote for itself!

            Roy Truelove added a comment - We're coming up on this ticket's 18th birthday.  It'll be old enough to vote for itself!

            Mike Fair added a comment -

            The value of this feature should be obvious, and not waiting for votes.  The concept of page history is crucial to the classical wiki culture.  Without it, the basic premise, and promise, of wiki-ness cannot be achieved.  And the current Confluence  scheme of browsing history is not sufficient by a long shot.  Line by line blame would be a big help, and should be easy because many SVN clients do it well with huge user bases.

            A related complaint / request.  I don't see how, in Confluence currently, I can keep track of a variety of non-text related page changes, including:

            1. moving a page (changing parent)
            2. deleting a page
            3. editing an attached file (e.g. gliffy pic, or excel doc using embedded editting)
            4. upload of a new version of an attached file
            5. deleting an attached file
            6. editing a macro

            Mike Fair added a comment - The value of this feature should be obvious, and not waiting for votes.  The concept of page history is crucial to the classical wiki culture.  Without it, the basic premise, and promise, of wiki-ness cannot be achieved.  And the current Confluence  scheme of browsing history is not sufficient by a long shot.  Line by line blame would be a big help, and should be easy because many SVN clients do it well with huge user bases. A related complaint / request.  I don't see how, in Confluence currently, I can keep track of a variety of non-text related page changes, including: moving a page (changing parent) deleting a page editing an attached file (e.g. gliffy pic, or excel doc using embedded editting) upload of a new version of an attached file deleting an attached file editing a macro

            I've added another vote on this feature. This would be really helpful.

            Roland Stahn added a comment - I've added another vote on this feature. This would be really helpful.

            Juergen Schwarz added a comment - - edited

            Imho, there is large interest in this idea, but too less people make their way to this issue and decide to create an account and to comment or vote here. If there were "Help to improve this page" buttons on those history pages leading to an anonymous voting page, we would get hundreds or thousands of votes.

            Juergen Schwarz added a comment - - edited Imho, there is large interest in this idea, but too less people make their way to this issue and decide to create an account and to comment or vote here. If there were "Help to improve this page" buttons on those history pages leading to an anonymous voting page, we would get hundreds or thousands of votes.

            I'm surprised there is not more interest in this idea. Page History is almost useless for understanding what actually changed in long pages with lots of edits. The 'blame' style would be really helpful.

            Kevin Campbell added a comment - I'm surprised there is not more interest in this idea. Page History is almost useless for understanding what actually changed in long pages with lots of edits. The 'blame' style would be really helpful.

            Sounds like a great Atlassian ShipIt! candidate

            Dmitry [Lucidchart] added a comment - Sounds like a great Atlassian ShipIt! candidate

            The svn blame implementation might be a helpful reference for the concept how to do that.

            Juergen Schwarz added a comment - The svn blame implementation might be a helpful reference for the concept how to do that.

              Unassigned Unassigned
              8d92d19feb5e Jeremy Higgs
              Votes:
              165 Vote for this issue
              Watchers:
              55 Start watching this issue

                Created:
                Updated: