-
Suggestion
-
Resolution: Answered
-
None
-
None
-
Standalone, Java version is 1.5.0_06, OS is Windows 2003 5.2
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
I'd like to be able to use the functionality in the recently-updated macro but to reverse the order of the function to indicate which child pages have not been updated in a long time.
We have a number of procedural pages listed in Confluence and I'd like to be able to highlight the pages which were modifed the longest ago in order to ensure the data in the pages is revisted regularly and updated as necessary. The returned data set would show the name of the page, the author and the last modifed date/time, just like the current macro, just in reverse order.
Ideally the macro could also include a parameter so that it would limit the return data set to a set number of entries.
{recently-updated:spaces=[Space to Search]|sort=reverse|show=[Number of entries returned]}- is duplicated by
-
CONFSERVER-20832 recent updated pages can not be sorted by ascending order(with the older at the top of list)
-
- Closed
-
-
- Closed
- relates to
-
- Closed
- was cloned as
-
- Closed
[CONFSERVER-10009] Sort by request for recently updated macro
Hi Penny,
Archiving Plugin for Confluence is to solve that particular problem you have.
It finds stale wiki pages, notifies their creators and last modifiers, and auto-archives them if no-one cares to update them. It is fully automatic and highly configurable, and it solves your problem more efficiently than manually sorting pages by reverse-update-time and deleting them one-by-one.
The plugin being a complete Content Retention tool offers more than this, please see the documentation.
Penny Lam
added a comment - I was searching for solutions to display our stale wiki pages however found this request last commented 2009 - are there no longer plans for the recently-updated:sort function to be re-introduced? Is there another way of having a similar view in 3.2?
Penny Lam
added a comment - I was searching for solutions to display our stale wiki pages however found this request last commented 2009 - are there no longer plans for the recently-updated:sort function to be re-introduced? Is there another way of having a similar view in 3.2? This issue is resolved with the latest version of confluence. The macro still has a label of recently updated even if the sorting is reverse which is a bit misleading but it works OK. Still not as preferable as a stale page macro that could be used to highlight pages that have npt been verified for a certain time period, but OK for the time being and as this issue was orginally posted in November of 2007 I'm not holding my breath for a solution.
Diane Sexton
added a comment - I was just checking out the use of the
{recently-updated}macro and in 3.0beta2-r3 it seems you can modify the order of the results e.g.
{recently-updated:sort=modified|reverse=true}However in a somewhat counter-intuitive way, the above query returns the results sorted by most recent first, if you remove the "reverse=true" parameter you get the updates sorted by longest-ago as requested by the OP. I would say what's needed is clearer documentation of the sort parameters in the macro documentation.
Diane Sexton
added a comment - I was just checking out the use of the
{recently-updated}
macro and in 3.0beta2-r3 it seems you can modify the order of the results e.g.
{recently-updated:sort=modified|reverse=true}
However in a somewhat counter-intuitive way, the above query returns the results sorted by most recent first, if you remove the "reverse=true" parameter you get the updates sorted by longest-ago as requested by the OP. I would say what's needed is clearer documentation of the sort parameters in the macro documentation. There was a similar request made for the functionality I am seeking which was posted here in May 2007 http://confluence.atlassian.com/display/DISC/Review+Stale+Content
Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.