Apply an archiving configuration to pages, page-trees or the result of a CQL query

Users want more granularity. Using the whole space as unit, we could apply configs to smaller units like individual pages, page trees or freely to pages matching a CQL,

Note: precedence should be well-defined when a page is tracked by multiple configs.

(Currently: you can define the settings per space and opt-out using the "noarchive" labels, but it is not possible to override the settings.)

Have more questions? Submit a request

5 Comments

  • 1
    Avatar
    Kristof Vandermeersch

    Related to this feature request:

    There are certain pages that are updated long ago, but they don't need to be updated.
    For example a parent page that only lists the child pages.

    In the Space statistics and emails, it appears such a pages are expired, but in reality, they are not.
    I would like to mark those pages with a label like "doesnotexpire" so those pages have a green (good) status.

    To achieve this, the current Space-level archiving configurations are fine, the implementation should be different:

    “If a page has the label ‘neverexpires’”, then leave the status on “up-to-date” (=ignore the other expiration criteria).

    (Or, this should be a checkbox in the GUI where Archiving Configurations are defined)

     

    Edited by Kristof Vandermeersch
  • 0
    Avatar
    Levente Szabo

    +1 vote. There was a duplicate feature request: "As a user, I want to apply the archiving configurations to only a certain page or pages (and their trees) within a space or cross-space."

  • 0
    Avatar
    Lyudmila Danchuk

    I'd love to see this feature! it would add flexibility in managing pages of different kinds.

    For example, a department has a separate space and they have some general info that doesn’t change very often and some internal monthly reports that should be updated regularly, so this would help them manage both kinds of pages easier.

    Another example -- priority: there can be pages that have high priority and should be always perfectly up to date. Would be nice to assign some custom label (for example, "high-priority") and set monthly or quarterly expiration while keeping, say, the yearly expiration rule for all the rest. 

  • 0
    Avatar
    Benjamin Eshet

    Joining this request!

    Parent pages should not be expired nor archived, and since there are a lot of these kind of pages, i would not expect my users to tag or label each one.

    Maybe if the expiration of a parent page would also be affected by its children?

  • 0
    Avatar
    Paula Dasch

    Joining this reqest!

    I plan to have standard configs for all confluence spaces with

    * time based checks for expired and not viewed pages in combination with
    * label based checks for archiving pages

    After some time, I want to have time based checks for archiving pages, too.

    Now I have the glossaries, which are just pages under a page called glossary, within a space:

    I would like the authors etc. being notified if the content is not viewed or expired, but I want the glossary entries NOT being archived because of time based checks, e.g if nobody has viewed it for 2 years.
    Is there a way to prevent pages to be archived after a time, if the whole space has an time based archiving config ? e.g. by some special labels? When I use "noarchive" the glossary is not checked at all. That is not what I want.

Please sign in to leave a comment.