Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-3707

Recently updated list on the dashboard should not show minor edits

    • 0
    • 0
    • 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 nice if the recently updated on the dashboard and the macro would default not show updates that were updated with the minor update check box set. A lot of people use the recently updated to browse for changes of interest and its a waste of time to see that someone fixed the spelling. An additional nice to have would be an indicator on the info tab recent changes and page history that indicated updates that were minor

            [CONFSERVER-3707] Recently updated list on the dashboard should not show minor edits

            Owen Beste added a comment -

            @Ben Richardson, I like that suggestion. The repetition of the same page really kills the usefulness of this macro when we have pages like daily scrum logs that get many updates every day. I don't want to see that page 10 times a day.

            Owen Beste added a comment - @Ben Richardson, I like that suggestion. The repetition of the same page really kills the usefulness of this macro when we have pages like daily scrum logs that get many updates every day. I don't want to see that page 10 times a day.

            Another way to solve this problem for us would be to only show the most recent update. For example, we currently see:

            Document C
            Document A
            Document B
            Document A

            Document A was added first, then B, an edit made to A and finally Document C added.

            The original Document A is redundant now. We'd prefer it be removed from the list and it becomes:

            Document C
            Document A
            Document B

            Each document is only shown once, and when it's edited it bubbles to the top.

            And by the way, the example I gave above is very simplified. Often the front page of our wiki looks like this (which is obviously not ideal):

            Document C
            Document C
            Document C
            Document C
            Document A
            Document A
            Document A
            Document A
            Document B
            Document B
            Document B
            Document A
            Document A
            Document A
            Document A

            The following would be so much nicer:

            Document C
            Document A
            Document B

            Ben Richardson added a comment - Another way to solve this problem for us would be to only show the most recent update. For example, we currently see: Document C Document A Document B Document A Document A was added first, then B, an edit made to A and finally Document C added. The original Document A is redundant now. We'd prefer it be removed from the list and it becomes: Document C Document A Document B Each document is only shown once, and when it's edited it bubbles to the top. And by the way, the example I gave above is very simplified. Often the front page of our wiki looks like this (which is obviously not ideal): Document C Document C Document C Document C Document A Document A Document A Document A Document B Document B Document B Document A Document A Document A Document A The following would be so much nicer: Document C Document A Document B

            It would be nice to at least be able to configure recently-updated and recently-updated-dashboard to either include or exclude minor updates...

            Deleted Account (Inactive) added a comment - It would be nice to at least be able to configure recently-updated and recently-updated-dashboard to either include or exclude minor updates...

            I don't agree, that this is only a minor issue.
            Minor Changes really spoil the recent-changes list and our employees start to complain that the recent-changes list is just spammed (in their words).

            Stefan Hansel added a comment - I don't agree, that this is only a minor issue. Minor Changes really spoil the recent-changes list and our employees start to complain that the recent-changes list is just spammed (in their words).

            I would prefer behavior where I can configure if I want to see minor updates in the Recently Updated list and in the Daily Updates email. The other option would be to indicate minor change by an icon. The email could also optionally include the comment, that can be filled in at saving the page.

            Petr Kohutek added a comment - I would prefer behavior where I can configure if I want to see minor updates in the Recently Updated list and in the Daily Updates email. The other option would be to indicate minor change by an icon. The email could also optionally include the comment, that can be filled in at saving the page.

            Matt B added a comment -

            I'm using content-reporter to do a news feed and I'd love to be able to make it so posts that only get minor edits don't appear in the feed.

            Matt B added a comment - I'm using content-reporter to do a news feed and I'd love to be able to make it so posts that only get minor edits don't appear in the feed.

            Added proper component.

            Per Fragemann [Atlassian] added a comment - Added proper component.

            Good points all. The reason it wasn't done this way from the outset was that the "minor edit" feature was added quite late in the development of Confluence, and so a lot of other things would have to be reworked for features like 'recently updated' to be able to distinguish betwen minor and major edits.

            Removing minor updates from the dashboard would certainly be an improvement, though.

            Charles Miller (Inactive) added a comment - Good points all. The reason it wasn't done this way from the outset was that the "minor edit" feature was added quite late in the development of Confluence, and so a lot of other things would have to be reworked for features like 'recently updated' to be able to distinguish betwen minor and major edits. Removing minor updates from the dashboard would certainly be an improvement, though.

            Bob Swift added a comment -

            I would add that updates that are the result of page renames should be considered minor and NOT show up on recently updated.

            Bob Swift added a comment - I would add that updates that are the result of page renames should be considered minor and NOT show up on recently updated.

            Precisely. I am surprised this behaviour wasn't there from the beginning. It almost defeats the purpose of the "Minor edit" feature; I believe Recent updates should list what is REALLY HAPPENING (new pages, major edits) rather then get a long list of minor changes as it is now. At least an option to supress minor edits from the list would be a big ++.

            Martin Blazek added a comment - Precisely. I am surprised this behaviour wasn't there from the beginning. It almost defeats the purpose of the "Minor edit" feature; I believe Recent updates should list what is REALLY HAPPENING (new pages, major edits) rather then get a long list of minor changes as it is now. At least an option to supress minor edits from the list would be a big ++.

              Unassigned Unassigned
              bob.swift Bob Swift
              Votes:
              48 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated: