.png)
Overview
The {my-recent-edits} macro lists content that has been recently created or edited by a specific user.
 | Deprecated This macro is deprecated from the 1.4 release, and may need to be manually enabled by a Confluence administrator. |
Usage
{my-recent-edits}
Parameters
| Parameter | Required | Default | Notes | Bubbles Version |
|---|---|---|---|---|
| default |  |
@self | The user whose recent edits are to be displayed:
|
1.1 |
| spaceKey | |
all spaces | By default, edits from all spaces will be shown. You can use this parameter to filter the list to edits from a single space if desired. | 1.1 |
| max | |
12 | The maximum number of items to display. | 1.1 |
| unique | |
true | If true only the latest copy of a page to be edited will be shown. If false all versions of a page that have been edited by the user will be displayed. | 1.1 |
Examples
Showing recent edits for a specific user
By default the recent edits of the logged in user will be shown. You can list recent edits for a specific user by specifying their user name, for example to show recent edits for a user with username "joebloggs" use:
{my-recent-edits:joebloggs}
You can show the recent edits for the person who created the page, news or comment in which the macro is used as follows:
{my-recent-edits:@creator}
Or you can show the recent edits for the person who created the space or community space as follows:
{my-recent-edits:@owner}
Showing recent edits for a specific space
Use the spaceKey parameter to filter results to a specific space by it's space key. For example, to filter the list to edits made in the FOO space, use:
{my-recent-edits:spaceKey=FOO}
Specifying the maximum number of results to display
Use the max parameter to define the maximum number of results to show:
{my-recent-edits:max=20}
Note: Internally the maximum number of items that can be read from the database is 150 or less - the actual maximum that can be displayed can be reduced to permission restrictions and/or filtering unique pages.
Hints and Tips
This macro retrieves its content from the Confluence database, this means it may be much slower the using the inbuilt Confluence {recently-updated} & {recently-changed} macros which make use of the Confluence search index to get their data. The benefit of using this macro is that is displays all of the content that a user has recently edited, the current index based macros can only display content that has been recently edited and is also the most recent version of the content.
If immediate updates are not vital, it would be worth caching the output of this macro with the cache macro.
