When a child is updated, it should not update its parent

We organize our pages in tree structure, but that does not mean that on parent pages are not also information stored, that are relevant for an expiration check. So for us the strategy, that parent pages are updated by a child page is not usable. For us each page must be handled separately without consideration of its child pages. 

(Note: this should be an ON/OFF switch in the archiving configuration.)

Have more questions? Submit a request

5 Comments

  • 0
    Avatar
    Bozo Norbert

    I support the proposal. It will be a usefull feature to have a On/Off radio button per space.

  • 0
    Avatar
    Michael Jerista

    For our purposes also a toggle (ON/OFF, as Aron suggests) for this feature would be AMAZING! Please please!

    Edited by Michael Jerista
  • 0
    Avatar
    Michael Jerista

    Forgot to give a little background: we are trialing this as it seems the most promising way available on the Atlassian Marketplace for us to do some proper content lifecycle gardening.

    However, our management has some misgivings about the accuracy of up-to-date-ness if each page is not evaluated separately...that parent pages auto-updating based on changes of children casts doubt...at least for the way we use Confluence and build our page trees.

    Is a feature like the one Aron suggests on the roadmap for BCA?

    Thanks for the time and feedback! 

  • 0
    Avatar
    Aron Gombas

    Michael,

    It is in the roadmap, yes, that's all I can say at the moment. (This is at the very core of the app, so it is far from trivial to change it.)

  • 0
    Avatar
    Dorothee Rothfuss-Bastian

    Actually we think that it would be helpful if parent pages were validated separately, so that their content is also monitored and the page status marker shows more reliable information for parent pages, too.

    However, we definitely do not want this to trigger archiving of "outdated" parent pages, since this would either lead to archiving of complete page trees (including child pages which are up-to-date) or to orphaned child pages, depending on whether the move to the archive takes place with or without the respective child pages. Both would result in chaos.

    Summing up, we would like separate monitoring for parent pages, but a blocker for archiving of parent pages as soon as they have child pages that are still up-to-date.

    Edited by Dorothee Rothfuss-Bastian
Please sign in to leave a comment.