• 47
    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? 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.

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

            Kyle added a comment -

            this would be fantastic. please implement this feature

            Kyle added a comment - this would be fantastic. please implement this feature

            jeffrey.wright added a comment - - edited

            Atlassian customer in 2006: "Please consider implementing a critical feature that is missing in your product." 

            Atlassian: "Please upvote it."

            Atlassian customer in 2024: "Did you ever get around to implementing that critical feature? It has been 18 years."

            Atlassian: "Please upvote it."

            jeffrey.wright added a comment - - edited Atlassian customer in 2006: "Please consider implementing a critical feature that is missing in your product."  Atlassian: "Please upvote it." Atlassian customer in 2024: "Did you ever get around to implementing that critical feature? It has been 18 years." Atlassian: "Please upvote it."

            Atlassian, can you elaborate on why it is hard to implement this feature or why it has been postponed so many times? (a blog post?)

            To me as a developer the problem sounds intriguing - I wonder where the complexity lies.

            Fabian Schneiter added a comment - Atlassian, can you elaborate on why it is hard to implement this feature or why it has been postponed so many times? (a blog post?) To me as a developer the problem sounds intriguing - I wonder where the complexity lies.

            Please, please add this feature. We have many long documents with many contributors, and I can't tell who wrote what. I want to be able to follow up with them to ask them about it.

            Kimberly Dauber added a comment - Please, please add this feature. We have many long documents with many contributors, and I can't tell who wrote what. I want to be able to follow up with them to ask them about it.

            I too suggest this feature to be available to make document writers/readers life easy.

            Ashish Jain added a comment - I too suggest this feature to be available to make document writers/readers life easy.

            Having a view for certain templates with the page history grouped like what you find in the Google Docs page history. 

            Jakob Hernandez added a comment - Having a view for certain templates with the page history grouped like what you find in the Google Docs page history. 

            Lol I love how I looked for an answer to this when I was fresh out of college... and here I am nearly 20 years into a career doing software development and I'm still waiting for this as a feature.

            Chris Portka added a comment - Lol I love how I looked for an answer to this when I was fresh out of college... and here I am nearly 20 years into a career doing software development and I'm still waiting for this as a feature.

            Chen Ni added a comment -

            Still not having this feature after 17 years??..

            Chen Ni added a comment - Still not having this feature after 17 years??..

            As a user

            • I open a page that lists office keys provided to people outside of the company.
            • Each item is added in separate revision of the document.
            • At one point I need to know who exactly from a contractor company received the key. 

            Expected:

            I annotate the document and see who added the line related to the key in question. I ask that person regarding the details. 

            Actual:

            I bisect the revision history to find the revision that added the desired line 🤦‍♂️

            Workaround:

            Ask in slack, and complain about how Confluence is useless for finding information  

            tomasfejfar added a comment - As a user I open a page that lists office keys provided to people outside of the company. Each item is added in separate revision of the document. At one point I need to know who exactly from a contractor company received the key.  Expected: I annotate the document and see who added the line related to the key in question. I ask that person regarding the details.  Actual: I bisect the revision history to find the revision that added the desired line 🤦‍♂️ Workaround: Ask in slack, and complain about how Confluence is useless for finding information  

            Definitely interested in this! It is critical to know which parts of a doc are new or outdated.

            Paul Baisley added a comment - Definitely interested in this! It is critical to know which parts of a doc are new or outdated.

            micseydel added a comment -

            It's not quite the same, especially for non-technical people, but Git with Obsidian does this. It's certainly not bleeding-edge technology.

            micseydel added a comment - It's not quite the same, especially for non-technical people, but Git with Obsidian does this. It's certainly not bleeding-edge technology.

            This was created in 2006 - come on - this isn’t a nice feature, it’s critical to understand how added what without bisecting the entire history.

            James Hanley added a comment - This was created in 2006 - come on - this isn’t a nice feature, it’s critical to understand how added what without bisecting the entire history.

            Just found this thread as I was trying to figure out how to enable this in Confluence. Wish I could upvote 1000x

            Taner Kipfer added a comment - Just found this thread as I was trying to figure out how to enable this in Confluence. Wish I could upvote 1000x

            Lu Zhang added a comment -

            I, too, strongly vote for this.  If this is too hard, even a more interactive expansion on the comparison page would allow me to do a manual binary search.  Imagine you need to find out who inserted a line.

            Lu Zhang added a comment - I, too, strongly vote for this.  If this is too hard, even a more interactive expansion on the comparison page would allow me to do a manual binary search.  Imagine you need to find out who inserted a line.

            It would be amazing to have this feature, not a day goes by that I don't think abt it.

            Todoran Victor added a comment - It would be amazing to have this feature, not a day goes by that I don't think abt it.

            Natasha Eilbert added a comment - - edited

            Strongly want this feature.  In addition to making it easy/clear who to ask questions about a given line, this feature could be transformational in incentivizing users in an organization to contribute to documentation by getting recognition / reinforcement for contributing.  The strength of our products and the ability for developers to develop quickly and efficiently, as well as for new developers to ramp up more quickly, is highly dependent on clear, well-organized, well-maintained documentation.  If there are auto-reinforcing (and simple) structures built in to our documentation such as this one, it would lead to better documentation, and more generally to our organizations being better-oiled machines.

             

            Also one suggestion for an implementation of this is to show the lastmodified user's avatar to the right of a given line (and possibly less recent other modifiers to the right of that?), with an on-hover showing their username.

            Natasha Eilbert added a comment - - edited Strongly want this feature.  In addition to making it easy/clear who to ask questions about a given line, this feature could be transformational in incentivizing users in an organization to contribute to documentation by getting recognition / reinforcement for contributing.  The strength of our products and the ability for developers to develop quickly and efficiently, as well as for new developers to ramp up more quickly, is highly dependent on clear, well-organized, well-maintained documentation.  If there are auto-reinforcing (and simple) structures built in to our documentation such as this one, it would lead to better documentation, and more generally to our organizations being better-oiled machines.   Also one suggestion for an implementation of this is to show the lastmodified user's avatar to the right of a given line (and possibly less recent other modifiers to the right of that?), with an on-hover showing their username.

            I'm stunned this doesn't have more votes. A week doesn't go by when I don't wish this were implemented. 

            John.Maddalozzo added a comment - I'm stunned this doesn't have more votes. A week doesn't go by when I don't wish this were implemented. 

            Denis Voirol added a comment - - edited

            It's been 14 years, since this request was first published (https://jira.atlassian.com/browse/CONFSERVER-8194)...

            The problem is:
            Always few people will ask for such feature, because also few are doing the painful "reviewing" job, and lot of people are misusing the wiki creating too much pages, instead of merging, correcting, keeping up-to-date.

            But a Blame feature will definitively ease to maintain the quality in the documentations.

            Denis Voirol added a comment - - edited It's been 14 years, since this request was first published ( https://jira.atlassian.com/browse/CONFSERVER-8194 )... The problem is: Always few people will ask for such feature, because also few are doing the painful "reviewing" job, and lot of people are misusing the wiki creating too much pages, instead of merging, correcting, keeping up-to-date. But a Blame feature will definitively ease to maintain the quality in the documentations.

            I need this feature.  The current history page is far too onerous to look through and understand what changed and when and by whom.

            Chris Portka added a comment - I need this feature.  The current history page is far too onerous to look through and understand what changed and when and by whom.

            Even if it was as simple as the source version being annotated like the `annotated` view in Bitbucket that would help answer basic questions like:

            • Who do I ask about this particular part of the documentation
            • When was the last part of this documentation updated...

            It would be a really cool feature

            Malcolm Watt added a comment - Even if it was as simple as the source version being annotated like the `annotated` view in Bitbucket that would help answer basic questions like: Who do I ask about this particular part of the documentation When was the last part of this documentation updated... It would be a really cool feature

            This would be an awesome feature, and would help to differentiate Confluence from its competitors.

            Matt Perrinel added a comment - This would be an awesome feature, and would help to differentiate Confluence from its competitors.

            Agreed with others here, feature would be greatly appreciated.

            Aurimas Dainius added a comment - Agreed with others here, feature would be greatly appreciated.

            hongyan added a comment - - edited

            We realy need this feature. it is too time-consuming to blame in a page.

            hongyan added a comment - - edited We realy need this feature. it is too time-consuming to blame in a page.

            d.andreev added a comment -

            We need this. 

            Right now I have to cycle through 20 versions of page to find a person to blame for an error. Do I need to write script for that? IMHO, no. 

            d.andreev added a comment - We need this.  Right now I have to cycle through 20 versions of page to find a person to blame for an error. Do I need to write script for that? IMHO, no. 

            This is needed badly because if many people work on a page intensively, thus creating many versions, the search through history takes so much time that it is not feasible any more...

            Markus Baumgartner added a comment - This is needed badly because if many people work on a page intensively, thus creating many versions, the search through history takes so much time that it is not feasible any more...

            Voted for that too

            Daniel Hauswirth added a comment - Voted for that too

            Do you guys read those at first place? I wouldn't bother upvoting otherwise.

            Damyan Yordanov added a comment - Do you guys read those at first place? I wouldn't bother upvoting otherwise.

            BobC added a comment -

            We need to quickly be able to find who a) last changed some text on a Confluence page, and/or b) first added the text.

            Sure, manually going back through the page history gets you there eventually.  But that's something computers should do for us, instead of using expensive engineer time, right?  Come on Atlassian, automate!

            BobC added a comment - We need to quickly be able to find who a) last changed some text on a Confluence page, and/or b) first added the text. Sure, manually going back through the page history gets you there eventually.  But that's something computers should do for us, instead of using expensive engineer time, right?  Come on Atlassian, automate!

            lei.liu added a comment -

            This feature is really help.  My company is using confluence,  and it's really inconvenient without this "annotated feature" when multi authors edit  one page. Please implement this feature.

            lei.liu added a comment - This feature is really help.  My company is using confluence,  and it's really inconvenient without this "annotated feature" when multi authors edit  one page. Please implement this feature.

            That would be very helpful, another vote for implementation.

            Tomasz Bogdański added a comment - That would be very helpful, another vote for implementation.

            Fred Cox added a comment -

            12 1/2 years since filing, and it still hasn't been implemented?

            Shame!

            Fred Cox added a comment - 12 1/2 years since filing, and it still hasn't been implemented? Shame!

            Another vote.

            I'm new to the Atlassian world and was surprised to discover this was not built in to wiki. SVN Blame and MS Word's 'track changes' have always been crucial elements to my workflow.

            Tim Ligtermoet added a comment - Another vote. I'm new to the Atlassian world and was surprised to discover this was not built in to wiki. SVN Blame and MS Word's 'track changes' have always been crucial elements to my workflow.

            Without this critical feature, the utility of Confluence is greatly diminished, IMO. Please move it up in your prioritized list of features. We just hit the "century mark" with my vote that takes it to 100. Time to make this happen, please!

            Darren Gardner added a comment - Without this critical feature, the utility of Confluence is greatly diminished, IMO. Please move it up in your prioritized list of features. We just hit the "century mark" with my vote that takes it to 100. Time to make this happen, please!

            I am at a loss as to how this is not a core utility of Confluence. This is a knowledge management system. Understanding who has added which piece of knowledge is of fundamental importance when working in a team. If the document you are reading needs clarification, you need to know who to request clarification from.

            Jackson Delahunt added a comment - I am at a loss as to how this is not a core utility of Confluence. This is a knowledge management system. Understanding who has added which piece of knowledge is of fundamental importance when working in a team. If the document you are reading needs clarification, you need to know who to request clarification from.

            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:
              375 Vote for this issue
              Watchers:
              135 Start watching this issue

                Created:
                Updated: