This version introduces a few changes as a preparation for the Confluence Server end-of-support.

Improvements

• On Confluence Server, a new message box informs administrators about the availability of the app's Cloud and Data Center versions.
• All URLs are updated to point to the documentation of the app's Data Center version.

See the full release notes →

This version introduces improvements on the "discuss" quick action, Java 17 support and various fixes.

Improvements

• The "discuss" quick action can start a discussion with the content owners with a single click.
• The "discuss" notification email shows the users that participate in the discussion. Everyone will see who else was invited to the discussion.
• When someone replies to an email sent by "discuss" using "Reply All" in the email client, all original recipients will receive the reply. Unlike the built-in "Share page" feature, which is essentially a one-time one-direction message, "discuss" now allows continuous group email conversations about the page!
• Java 17 support.

Security fixes

• Updated dependency: Moment.js.

Bugfixes

• Fixed: When a space is totally empty (contains zero pages), its content quality becomes 50% unexpectedly.
• Fixed: The "Trusted group" selector doesn't contain any option in its drop-down, unless there are at least 3 characters entered.

See the full release notes →

This version is a compatibility release for Confluence 8.0.

See the full release notes →

This version is a compatibility release for Confluence 7.14.

See the full release notes →

This version is a compatibility release for Confluence 7.13.

See the full release notes →

This version is a compatibility release for Confluence 7.12.

See the full release notes →

This version is a compatibility release for Confluence 7.7.

See the full release notes →

This version introduces the concept of content owners.

Content owners are one or more manually selected users who are responsible for the content in a single page or in a whole page tree. They can optionally be notified when the page becomes not-viewed, expired or archived. The concept is similar to, for example, the author or the last modifier of the page, but while these are "implicit" roles (determined automatically), page owners are "explicit" (selected manually).

New features:

• Content owners.

Notable changes:

• Terminology change: "archiving job" is now called "content lifecycle job".
• Terminology change: "archiving event" is now called "content audit log event", while "content events" (as a screen title) becomes "content audit log".

Bugfixes:

• Fixed: when collapsing the node of a last sibling in the Content Status Browser, sometimes all nodes "below it" disappear from the UI.

See the full release notes →

This version is a compatibility release for Confluence 7.6.

Atlassian has fixed the bug that was introduced in Confluence 7.5.0 and made us to disable the "hide archive space" feature in the previous version of Better Content Archiving for Confluence. In this release we re-enabled that feature.

IMPORTANT: If you are using Confluence 7.5.0 or 7.5.1, don't forget to upgrade your Confluence version to 7.5.2 or newer.

See the full release notes →

Recently released Confluence 7.5.0 introduced a bug around archiving spaces. The bug broke the "create archive space" mechanism in the Better Content Archiving app.

While we work with Atlassian on the bugfix, this temporary app version helps you to upgrade to Confluence 7.5.0. It disables only a fairly minor app feature that's affected by the bug, but even that feature can be worked around manually.

As soon as the bug is fixed by Atlassian, we will release another app version that re-enables the feature.

See the full release notes →

This version introduces compatibility with the so-called read-only mode in Confluence.

New features:

• Support for Confluence read-only mode.

See the full release notes →

Bugfixes:

• Fixed: the "Trusted group" field in the "Settings" screen cannot be used with 30,000 groups
• Fixed: when the secure administrator session times out, saving blacklisted spaces will reset that to an empty list

See the full release notes →

This version is a compatibility release for Confluence 7.0.

IMPORTANT: as there is a change around job schedules, make absolutely sure you check out the upgrade guide!

Bugfixes

• Fixed: the "Last Execution" column in the Scheduled Jobs screen is empty for 2 of the app's jobs

See the full release notes →

This release introduces "quick actions" which significantly ease controlling the lifecycle of pages. "Quick actions" is a concept that we have been experimenting with for a couple of months, and now release it for the public to elevate the end-user experience to a new level.

New features

• Quick actions

Improvements

• User manual section of the "Move" strategy is rewritten with more details on copying and synchronizing ancestor pages.
• New user manual section added about the permissions required to restore pages.

See the full release notes →

This release comes with two valuable features frequently requested by the user community that are super-important for administrators of Confluence sites with many spaces and many users.

Plus, an improvement related to the "archive" watermark and permission copying, furthermore a small bugfix.

New in this release

• Default archiving configuration (automatically set for newly created spaces)
• Trusted group (allows restricting the space administrators who can configure and run archiving in their spaces)

Improvements

• The "archive" watermark is visible in all spaces with the "archived" status (not only in the spaces created by the Better Content Archiving app)
• When creating archive spaces, anonymous and "all authenticated users" type permissions are not copied

Bugfixes

• Fixed: by manually rewriting the space key from "Foo" to "FOO" in the URL, it is possible to set an archiving config to the same space multiple times

See the full release notes →

This release comes with a super-popular feature request implemented to protect personal information. Thanks to Enrico, Florian, Ganna, Karl, Katharina, Michael, Niko, Ralf for helping us with detailing their requirements!

Plus, most visibly, the app got a new name!

New in this release

• Bye-bye "Archiving Plugin for Confluence"! Hello "Better Content Archiving for Confluence"!
• Data privacy (for GDPR)

See the full release notes →

As you probably know, Archiving Plugin already supports Confluence Data Center deployments (i.e. clustered Confluence). To be precise, those are supported since app version 7.0.0 (released in May 2017).

In 2018, Atlassian re-launched its Data Center program and introduced new development and testing criteria for "Data Center approved apps". This version is the official release for the revised program, tested to live up to the rigorous demands of Data Center environments.

New in this release

• Archiving Plugin is a Data Center approved app!

See the full release notes →

This version introduces a few changes as a preparation for the Confluence Server end-of-support.

Improvements

• On Confluence Server, a new message box informs administrators about the availability of the app's Cloud and Data Center versions.
• All URLs are updated to point to the documentation of the app's Data Center version.

See the full release notes →

This version introduces improvements on the "discuss" quick action, Java 17 support and various fixes.

Improvements

• The "discuss" quick action can start a discussion with the content owners with a single click.
• The "discuss" notification email shows the users that participate in the discussion. Everyone will see who else was invited to the discussion.
• When someone replies to an email sent by "discuss" using "Reply All" in the email client, all original recipients will receive the reply. Unlike the built-in "Share page" feature, which is essentially a one-time one-direction message, "discuss" now allows continuous group email conversations about the page!
• Java 17 support.

Security fixes

• Updated dependency: Moment.js.

Bugfixes

• Fixed: When a space is totally empty (contains zero pages), its content quality becomes 50% unexpectedly.
• Fixed: The "Trusted group" selector doesn't contain any option in its drop-down, unless there are at least 3 characters entered.

See the full release notes →

This version is a compatibility release for Confluence 8.0.

See the full release notes →

This version is a compatibility release for Confluence 7.14.

See the full release notes →

This version is a compatibility release for Confluence 7.13.

See the full release notes →

This version is a compatibility release for Confluence 7.12.

See the full release notes →

This version is a compatibility release for Confluence 7.7.

See the full release notes →

This version introduces the concept of content owners.

Content owners are one or more manually selected users who are responsible for the content in a single page or in a whole page tree. They can optionally be notified when the page becomes not-viewed, expired or archived. The concept is similar to, for example, the author or the last modifier of the page, but while these are "implicit" roles (determined automatically), page owners are "explicit" (selected manually).

New features:

• Content owners.

Notable changes:

• Terminology change: "archiving job" is now called "content lifecycle job".
• Terminology change: "archiving event" is now called "content audit log event", while "content events" (as a screen title) becomes "content audit log".

Bugfixes:

• Fixed: when collapsing the node of a last sibling in the Content Status Browser, sometimes all nodes "below it" disappear from the UI.

See the full release notes →

This version is a compatibility release for Confluence 7.6.

Atlassian has fixed the bug that was introduced in Confluence 7.5.0 and made us to disable the "hide archive space" feature in the previous version of Better Content Archiving for Confluence. In this release we re-enabled that feature.

IMPORTANT: If you are using Confluence 7.5.0 or 7.5.1, don't forget to upgrade your Confluence version to 7.5.2 or newer.

See the full release notes →

Recently released Confluence 7.5.0 introduced a bug around archiving spaces. The bug broke the "create archive space" mechanism in the Better Content Archiving app.

While we work with Atlassian on the bugfix, this temporary app version helps you to upgrade to Confluence 7.5.0. It disables only a fairly minor app feature that's affected by the bug, but even that feature can be worked around manually.

As soon as the bug is fixed by Atlassian, we will release another app version that re-enables the feature.

See the full release notes →

This version introduces compatibility with the so-called read-only mode in Confluence.

New features:

• Support for Confluence read-only mode.

See the full release notes →

Bugfixes:

• Fixed: the "Trusted group" field in the "Settings" screen cannot be used with 30,000 groups
• Fixed: when the secure administrator session times out, saving blacklisted spaces will reset that to an empty list

See the full release notes →

This version is a compatibility release for Confluence 7.0.

IMPORTANT: as there is a change around job schedules, make absolutely sure you check out the upgrade guide!

Bugfixes

• Fixed: the "Last Execution" column in the Scheduled Jobs screen is empty for 2 of the app's jobs

See the full release notes →

This release introduces "quick actions" which significantly ease controlling the lifecycle of pages. "Quick actions" is a concept that we have been experimenting with for a couple of months, and now release it for the public to elevate the end-user experience to a new level.

New features

• Quick actions

Improvements

• User manual section of the "Move" strategy is rewritten with more details on copying and synchronizing ancestor pages.
• New user manual section added about the permissions required to restore pages.

See the full release notes →

This release comes with two valuable features frequently requested by the user community that are super-important for administrators of Confluence sites with many spaces and many users.

Plus, an improvement related to the "archive" watermark and permission copying, furthermore a small bugfix.

New in this release

• Default archiving configuration (automatically set for newly created spaces)
• Trusted group (allows restricting the space administrators who can configure and run archiving in their spaces)

Improvements

• The "archive" watermark is visible in all spaces with the "archived" status (not only in the spaces created by the Better Content Archiving app)
• When creating archive spaces, anonymous and "all authenticated users" type permissions are not copied

Bugfixes

• Fixed: by manually rewriting the space key from "Foo" to "FOO" in the URL, it is possible to set an archiving config to the same space multiple times

See the full release notes →

This release comes with a super-popular feature request implemented to protect personal information. Thanks to Enrico, Florian, Ganna, Karl, Katharina, Michael, Niko, Ralf for helping us with detailing their requirements!

Plus, most visibly, the app got a new name!

New in this release

• Bye-bye "Archiving Plugin for Confluence"! Hello "Better Content Archiving for Confluence"!
• Data privacy (for GDPR)

See the full release notes →

As you probably know, Archiving Plugin already supports Confluence Data Center deployments (i.e. clustered Confluence). To be precise, those are supported since app version 7.0.0 (released in May 2017).

In 2018, Atlassian re-launched its Data Center program and introduced new criteria for "Data Center readiness". This version is the official release for the revised Data Center Ready program.

New in this release

• Archiving Plugin is Data Center Ready (again)

See the full release notes →

This is primarily a compatibility release with no major changes in features.

Page view initialization

As the most popular feature request, this version introduces a new feature to solve the "abandoned pages" problem! You can now sensibly initialize the last page view information when building or re-building the content event index.

Multiple supervisors per archiving configuration

You can select multiple users as supervisors in any archiving configuration. This allows making more than one person responsible for the space, resulting in even better content quality.

Improvements

• Content Quality Statistics and Start Archiving screens give a clear error message when long-running tasks cannot be started due to missing actors (i.e. when the "confluence-administrator" groups that contains the super-user does not exist or does not contain at least one valid user account).
• Archiving configuration editor gives more intuitive validation messages (related to the page view- and update intervals for various triggers).

See the full release notes →

This is primarily a compatibility release with no major changes in features.

Distinct style for archive spaces

In the past, users unwantedly edited archive pages because they didn't realize that they are in an archive space's context. Now the add-on gives a clear, but non-obtrusive style (yellowish background color plus an expressive watermark) to archive pages.

Intelligent label filtering

From now on, when a page is moved or copied to the archive space, its labels are filtered to avoid unexpected behaviour.

Improvements

• Notification email templates have access to the archiving configuration (e.g. the "page view alert" setting)

Bugfixes

• Fixed: Inline comments become regular page comments in the archive space
• Fixed: Favorite pages are listed twice in the favorites list (once from the fresh space and once from the archive space)
• Fixed: Page renaming unexpectedly updates the last update date of the linked pages
• Fixed: Incomplete page and attachment data causes "Cannot set non-null field UPDATE_DATE to null" error while re-building the content update index

This is primarily a compatibility release with no major changes in features.

Bugfixes:

• Fixed: "Data integrity error in migrated archiving configuration" error when upgrading to add-on version 7.0.0

Support for Confluence Data Center (cluster)

We are happy to announce that this add-on version implements the long awaited support for Confluence Data Center deployments!

Over the last 10 months we put insane efforts to the 6.x releases (the grounding work) and to this new release, aiming to provide Content Lifecycle Management for Confluence clusters. 6.x allows to efficiently process millions of pages, while 7.x allows to do that over multiple Confluence nodes.

Learn more about archiving in Data Center deployments

Compatibility with Confluence 6.2

This version is also a compatibility release for Confluence 6.2.

Bugfixes:

• Fixed: Page Status Indicator is displaying an error for previous page versions
• Fixed: The content of the Page Status Indicator overlay is "zoomed in" when the Comala Workflows add-on is installed

Bugfixes:

• Fixed: "Comparison method violates its general contract" errors in Confluence core when Archiving Plugin screens are accessed (reported to Atlassian as CONF-45910)
• Fixed: Page edits with "Notify watchers" unchecked (also known as "minor edits") do not refresh the page's Last Update date

Configurable data limits

In the previous add-on version (6.0.0), we introduced the so-called data limits to save your server from wasting computing resources (CPU, memory) on irrelevant data. In this version, we rebuilt the end of the data processing pipeline for even more performance and lower memory footprint. Using the new configurable data limits, several thousand notification emails (for hundreds of spaces and several hundred thousand pages) were sent without problems in our internal load tests.

Bugfixes

• Fixed: Hibernate "owning Session was closed" error while collecting the addressees for notification emails.
• Fixed: Empty page lists in archiving events cause NPEs with Oracle.
• Fixed: Blacklist checking crashes on the spaces that have no description object associated with (i.e. their data is corrupt).
• Fixed: When all spaces are blacklisted, the Content Quality Stats screen misleadingly suggests that the system is in an unindexed state.

Concept of the Content Update Index

The introduction of the Content Update Index is the single most important change in this release. Without going into details, the index maintains the last update information (who updated what, when?) in a scalable and searchable way, eliminating expensive page tree traversals.

Data limiting

Starting from this release the add-on reduces the data to the "actionable" size. It both prevents your users from information overload and your system from wasting resources on useless work.

Bugfixes

• Fixed: in previous versions, no pages found to archive if the archiving configuration specified the "AND" operator between the Page Archiving triggers "Not viewed for N days" and "Not updated for M days", and one of those were disabled. (This was a major bug with a simple workaround: turn the operator to "OR".)
• Fixed: Content Tools → Page Status is shown, but disallowed for regular users.
• Fixed: Manage blacklisted spaces link is displayed for space administrators.

This version focuses on improving the integration with various space themes. By introducing the Brikit Theme Press support, Archiving Plugin now supports all major Confluence themes, including built-in types and the types provided by 3rd party add-ons.

Support for Brikit Theme Press 2.0.2

Starting from this version, you can use the Archiving Plugin also in the spaces relying on the popular Brikit Theme Press add-on.

Updated from Bitvoodoo Enterprise Theme 5.1.2

We updated this integration to the latest Enterprise Theme add-on version:

• Fixed: Page Status Indicator is not visible
• Fixed: "Archiving" tab in Space Tools is duplicated

Compatibility tested with Refined Theme 5.1.3 and Scroll Versions 3.3.2

We also verified the Archiving Plugin working correctly with these two popular theme add-ons. (OK, Scroll Versions is not a theme add-on by design, but this also introduces its own theme.)

This version is a compatibility release for Confluence 6 with additional minor bugfixes.

Differences due to collaborative editing

Confluence 6 introduced collaborative editing. The only difference it means for the Archiving Plugin is that any "partial page update" will update the last update timestamp of the edited page. In other words, when any of the users editing the same page at the same time saves his/her "partial" changes, that will make the page current. From that point, everything works just as in previous add-on versions.

Bugfixes

• Fixed: Page titles in page lists (like "expired pages") overlap with the page icons
• Fixed: When archiving page comments, certain "mentions" result in unwanted mail notifications
• Fixed: "Archiving" and "Archiving configuration" tabs are displayed in archive spaces

Bugfixes:

• Clicking "Start Archiving" in Confluence 5.7 will not stop with NoSuchMethodError.
• Page Status Browser is now visible in spaces using recent versions of the Bitvoodoo Enterprise Theme.

Archiving strategies

Starting from this release, there are 3 ways to archive pages:

• Move them to an archive space ("Move" strategy),
• Copy them to an archive space and delete them in the fresh space ("Copy and Trash" strategy)
• Or just delete them in their original space ("Trash" strategy)

Each of these have their own merits, but "Move" is the new default, as it fits the most use cases the best.

"Move" implements the most requested feature to preserve the full version history for archived pages. Thanks for everyone asking for this, we appreciate your patience and your help in finding the perfect roadmap for the add-on! Keep it comin'!

After upgrading to this version, consider switching existing archiving configurations to "Move" (guide).

Performance improvements in archiving

The archiving logic used in previous add-on versions is now called "Copy and Trash". Even this strategy is faster than it was before, but "Move" is faster in most circumstances and "Trash" is blazingly fast.

Bugfixes:

• This release fixes the NullPointerException problem that occurred when keys of deleted spaces were in the global-configuration-to-space-key mapping. (The code tried to decide if a deleted space is currently blacklisted and failed on that check.)

Blacklisted spaces

Turn off the Archiving Plugin for those spaces that are not relevant or have corrupt data, to improve the add-on performance and stability.

Support for the Scoll Versions Theme and the Bitvoodoo Enterprise Theme

This release adds official support for two highly popular 3rd party space themes.

Customizable notification emails

The content of all 4 notification emails types (non-viewed pages, expired pages, archived pages, skipped pages) are editable via a web based editor. In previous versions, you could edit the templates by exploding the plugin JAR, but localization, adding your own content is now super easy.

Automatic archiving on a specific date

Just add the label "archive-15/12/1" and the page (plus its descendants) will be automatically archived on 1 Dec 2015. It couldn't be more fire-and-forget. Use it carefully, and make sure you don't shoot yourself in the foot.

A new screen, available using the "Spaces" link from the "Global Configurations" screen, allows quickly applying a global configuration to multiple spaces in one go. This is a huge time saver if you have a large number of spaces.

(This was the most popular feature request at the time. We take your feedback seriously, thanks!)

This release also features some bugfixes, most importantly a fix for an infamous Java 7/8 incompatibility problem.

Fixed issue:

• Page Status Cache tolerates usernames containing space characters (should never happen, but it actually does!).

Page status browser

Conveniently browse through the pages in a space, with their real-time status, last update dates, last view dates displayed.

Page status indicator

Page status is also shown in the top-left corner of the content pane.

"Archive" quick-action in notification emails

Adding the "archive this page" label is now available in the notification emails! While looking at the list of expired pages, you can update or archive them with a single click.

Trigger precedence changed

The evaluation order of the archiving sub-triggers is now more intuitive. Recommendation: review your archiving configurations that use all the 3 sub-triggers!

REST API

Although the primary aim of the new API is to provide back-end for the plugin's own user-interface, you are also welcome to use it for your reporting and integration purposes.

This is primarily a compatibility release with no major changes in features.

Fixed issues:

• Expired HTTP sessions caused broken global archiving configurations (sometimes)
• When the attachment's number of bytes were not equal to the its filesize property (as known in the database), archiving failed. Now, it tolerates this, the actual number of bytes takes precedence and it logs these attachments with WARN level. It should normally never happen, only if someone modified the attachment files directly in the file system.

Fixed defects:

• "Archiver user" gets unauthenticated after the archiving job is completed. (It may have caused some conflicts with other background jobs in previous versions.)
• Validation of the "period lengths" in lifecycle rules is less strict. (These were overly strict in previous versions, not allowing certain valid configurations.)

NEW TRIGGER: ARCHIVE PAGE IF NOT VIEWED IN LAST N DAYS

You can flexibly combine this new trigger with others, like "and if it has not been updated in the last Z days or has been labelled with 'archive'".

"PAGES NOT VIEWED RECENTLY" LIST DISPLAYED INSTANTLY

The count of "pages not viewed recently" is now displayed in the Content Quality Statistics table, and it contributes to the overall quality metric. Click that link to view the exact page list.

SPACE- AND PAGE ARCHIVING IS MORE ROBUST

The rewritten code is more fault tolerant and handles concurrency better.

NO EMAIL NOISE

No unwanted notification emails are sent at page archiving (creations, deletions), comments, attachment or mentions.

MANY-MANY SMALLER IMPROVEMENTS

Numerous fixes and changes were made on the UI (ex: convenience links, hiding the archiving functionality for archive spaces), on Internet Explorer compatibility (ex: non-clickable buttons) or in the internals (ex: improved logging).

This version is compatible with the Confluence 5.6 line. It also comes with a couple of minor cosmetic bugfixes.

NEW CONFIGURE ARCHIVING INTERFACE

In 4.0.0, the new configuration experience is based around the concept of triggers ("if a page is older than 10 days" or "if a page labelled with 'foo'"...) and actions (...then "notify its last modifier"), allowing fine-grained settings and eliminating confusion.

The rules of "who receives what email" are 100% configurable.

SUPERVISORS

To send notifications to users that are not "directly" related to the content (not authors, etc.), configure so-called supervisors.

To route all notifications to a single external mailbox, just set up a Confluence user with that email address and select that as supervisor.

SELECTABLE ARCHIVER USER

Previously, archiving operations (like copying and deleting pages) were executed by a user account automatically selected by the plugin. It lead to some misunderstanding.

The archiver user can now be manually picked. Tip: set up an intuitively named user account (ex: "Wiki Archiver") for that.

...oh, did you see our new docs?

This release is updated for the Confluence 5.5 line.

In addition, some minor internal glitches were also fixed.

This version is a maintenance release, that fixes a problem with the "page view tracking" feature, when used with MS SQL on very large spaces.

This version is a maintenance release, that fixes a problem with the "page view tracking" feature, when used with MS SQL on very large spaces.

Fixed in this release

FIXED: iIn previous versions, page view tracking caused null-pointer exceptions in spaces where anonymous access was allowed.

This plugin version introduces a new feature called page view tracking to find those Confluence pages that were not viewed by anybody for a period of time.

Discover both outdated (not edited by anyone) and irrelevant (not viewed by anyone) wiki content. Archive that easily to prevent efficiency, productivity and consistency problems.

This is a compatibility release for the Confluence 5.2 product line. 

A new "Getting started" page was also added in this release. It will both kickstart new users with the plugin, and further educate existing users on plugin features, documentation and use cases. The guide is displayed when the plugin installation or -update was finished, and can be accessed any time later from the Manage Add-ons screen.

We also made the plugin more error-tolerant to pages and attachments with missing "last modified" dates. Some users reported failures with that kind of corrupted data, and although those could have been easily fixed, we improved the robustness of the plugin, as well.

This is a maintenance release for 2.2.0.

It fixes the only reported problem in that release: the Archiving link is now displayed correctly also in the spaces using the Documentation Theme.

This is a compatibility release for the Confluence 5 product line. 

The plugins user interface and experience was rebuilt to follow the current Atlassian Design Guidelines. 

Also, the plugin was transparently adapted to the internal changes in Confluence 5.

"Archive space" status

Confluence 4.3 introduced a smart flag to mark archive spaces. Setting this, the corresponding space will disappear from the usual navigation paths, from search results, from dashboards and from activity streams. The Archiving Plugin now sets this flag to hide the archive spaces, instead of the manipulating the permissions, as done previously.

Major bugfixes

We fixed several problems to make the plugin more robust and our users happier:

• Space administrators can modify archiving settings for their spaces. (You don't have to be a Confluence administrator to do this.)
• The archiver automatically fixes all problems that occur when the page hiearchy was tweaked in the fresh space between two archiving runs. (It was a hard to track problem, especially in large spaces.)
• The archiver intelligently handles mixed case page names.
• No more exceptions while removing the default homepage of archive spaces.

Commercial support

Beginning from this version, Midori provides commercial support for the Confluence Archiving Plugin. Benefits? Frequent updates to new Confluence versions, quick problem resolution, and direct help from the engineers who develop the plugin.

This is our biggest release since 1.0.0:

• Reusable global configurations: define global archiving configurations and reuse those in multiple spaces, for consistency and ease.
• You can now effectively hide archive spaces. (Making them visible only for administrators removes the duplicated content and duplicated search hits for regular users.)
• Freshness analytics in the web UI and emails. Find out which are the most outdated spaces and space categories, in seconds.
• "Archiving reason" for archiving policies: you may optionally require your users to post a comment to explain why to archive a page. If it is missing, the page is skipped.
• All background jobs can be configured through the Confluence job administrationinterface. Customize archiving schedule as you wish.
• "Who archived the page"in the notification emails: see this important piece of information for pages that have been archived manually by a user, not automatically by the job.
• Event streamsmaintain the archiving history by space and globally: what pages expired, were archived, were updated or were skipped and when.
• You can now start archiving globally with a single click. (In previous versions it was only possible for individual spaces.)

(This release has been generously sponsored by Appelsiini Finland Oy.)

Confluence Archiving Plugin is now compatible with Confluence 4.

The periodic job that detects and optionally archives outdated content is now listed in the Scheduled Jobs screen of the administration console. You can configure it just like any other job in Confluence: run it as frequently as you want, and start it in whenever your team is not concurrently updating content.

Email templates are also updated to follow the new look of notification mails sent by Confluence 4.

Known issues: the Confluence Mentions Plugin and the Confluence Jira Connector Plugin throw NullPointerException's while archiving. Luckily, those exceptions can be safely ignored.

These are caused by bugs in those two other plugins. There is no workaround we could make.

We reported the problems to the Atlassian team. Please vote on these issues to see them fixed as soon as possible:

• https://studio.plugins.atlassian.com/browse/MNTS-18

• https://jira.atlassian.com/browse/CONF-25023

Notification emails look nicer, and give you more information in version 1.2.

They tell you what pages expired, when they have expired, who made the last update and when, and when will they be auto-archived if ever. All this information is available per space in an easy to read format.

This makes it easier to decide whether you have to update the expired pages immediately, or whether updates can wait a little.

Support for noarchive and noarchive-single.
Displaying reason in all notification mails.
Testing with the Confluence 3.x line.

RC updated to work with Confluence 2.10.