Users would like to configure and customize the wording of archiving labels, as the default labels (like archive) can conflict with existing ones.
Make archiving labels customizable
-
Robin Gojowy This would great , the actualy labels are very cryptical and user do not understand them.
-
Matthew Warren Meeting notes are automatically labeled by Confluence with meeting-notes tag. Having the ability to exclude pages with the meeting-notes tag from lifecycle checks would be useful in our organization.
Thank you
-
Aron Gombas UPDATE: We have released the Better Content Archiving app's cloud version just a few weeks ago. It addresses many points criticized in the Data Center version, including also this one.
(Our plan is that, if there is interest, we will back-port the most valuable changes from the Cloud version to the Data Center one.)
In the cloud version, each status is defined with a customizable CQL query. It means that you can completely re-configure under what conditions a page gets changed to the "To archive" status.
For example a CQL like this can test on the existence of any of the 3 labels:
label in ("archive", "garbage", "irrelevant")
But, you can completely get rid of testing on labels and rely only on the archiving date selected by the user:
arch.archivingDate < now()
Or, combine using the hand-picked archiving date and also archive pages older than 1000 days:
arch.archivingDate < now() or arch.event.lastUpdatedOn < now("-1000d")
Or, ... there is a billion things you can do! Because of the flexibility of CQL searches, you can customize not only the labels, but the complete condition that determines what should be in the "to archive" status!
3 Comments