--- title: "Enhanced Page Change History Macro" canonical: "https://doc.utingu.com/space/URD/786440/Enhanced%20Page%20Change%20History%20Macro" format: markdown --- --- ## Contents --- ## About Enhanced Page Change History Macro --- ## Page Change History Filtering If multiple filter options are configured, they will be applied using an **AND** logic. For example, if both Comment Text and Version Authors are specified, the results will include only the versions created by the selected author(s) that also contain the specified comment text. > Macro (rw-ui-textbox-macro) > > All configuration options are optional. If no filters are applied, the full page history will be displayed in the version history table. **Below are the main features of the macro configuration:** ### Version Count Set up the macro to display only the most recent page versions instead of the entire history table. Entering a number in this setting limits the **maximum number of versions** displayed in the page history table. This limit is applied **after** all other filters have been processed. **Example:** Display only the last 5 versions of the page history. ### Comment Text This option filters page versions based on the comments entered by users when saving page versions. It performs a simple, case-insensitive text match. For example, if a comment is **"Another comment on this page"** and the **Comment Text** filter is set to **"comment"**, that version will be included in the results. **Example:** Filtering page versions where the comment contains the word *"comment"*. ### Version Authors Display only the specified authors of page versions. Filters the page history table to show only versions created by the selected author/s. Multiple page authors can be selected **Example:** In the blog page example below, the history is filtered to display versions authored by the Utingu Software Sales and Support accounts. ### Page Collaborators This macro also allows filtering by **multiple users** who collaborated on a specific page version. If a selected user contributed to a version alongside other collaborators, the page history table will display **all collaborators** involved in that version. > Macro (rw-ui-textbox-macro) > > To use this feature, the “Collaborators” column must be visible, make sure the checkbox is unchecked in the “Hide Columns” settings. **Example:** Displays page versions where the Support and Sales accounts were listed as collaborators. ### Show Myself In Checkboxes #### Authors When this checkbox is selected, the page history table will filter results to show only versions **authored by the current user (you)**. If used in combination with the **Version Authors** field, the table will display versions authored by **both the current user and any users selected** in the Version Authors field. **Example:** Displays the last five page versions where the user (**you)** is the author. #### Collaborators If this checkbox is selected, the page history table will filter to show versions where the **current user (you)** is a page collaborator. When used together with the **Page Collaborators** field, the table will display versions where **either you or the selected collaborators** contributed. Please note that displaying the **Collaborators** column in the page history table may affect the macro’s performance, see the **Performance Considerations** section for details. > Macro (rw-ui-textbox-macro) > > This checkbox appears only when the **Collaborators** option in the **“Hide Columns”** settings is **unchecked**. **Example:** Displays the page versions where the user **(you)** has participated as a page collaborator. ### Hide Columns This checkbox setting lets users choose which columns to hide in the page version table results. The **page version number** column is the only one that cannot be hidden. The following columns are available to be hidden from the page history table: **Example:** Displays the last five page versions, with only the Version, Date, and Collaborators columns visible in the table. ### Version Rows Per Page This macro supports pagination for the page history table. By entering a number greater than zero in this field, you can limit the number of version rows displayed per page. This helps reduce the screen space the macro occupies while still allowing users to access larger result sets. **Example:** The page below has 98 versions, with 15 rows displayed per page in the table. ### Suppress Row Highlighting Alternate row coloring is applied to the page version history table to distinguish each page version. When multiple collaborators exist for a single version, additional rows with the same color are displayed. If you prefer to disable this alternate coloring, you can do so by checking this box. **Example:** The table below shows the same paginated version as above, but with row highlighting turned off. --- ## Performance Considerations If the **“Collaborators”** checkbox in the **“Hide Columns”** configuration is unchecked, the page version collaborators will be shown in the page history results table. On Atlassian Cloud, many Marketplace Apps rely heavily on API calls to fetch the data they need. Retrieving collaborator information for each page version requires a separate API call per version. For pages with many versions, this can slow down the macro’s performance. During this process, users will see a progress bar indicating how many versions have been processed. Once this initial loading is complete, subsequent page refreshes in the same browser session should load faster, as the version information is cached locally in the browser. Therefore, if the **“Collaborators”** column is displayed, users may encounter the progress bar when first loading the page. Refreshing the page within the same session should improve rendering speed. ---