Restrict the manual start of the archiving job to a specific time range

As a user, I'd like to restrict what time of day the archiving job can be run.

Have more questions? Submit a request

6 Comments

  • 0
    Avatar
    Aron Gombas

    I'm not sure what is the specific request here.

    You can schedule the archiving job like any other Confluence job, which allows you this run nightly: https://confluence.atlassian.com/doc/scheduled-jobs-96567525.html

    Am I missing something?

  • 0
    Avatar
    Jay Louvis

    The concern here isn't that we can't run off hours or need a way to do so, it's that we want to prevent users from manually executing an archive job during certain hours as it can impact performance. Any space admin can go into the space settings and kick off an archive job at will.

    There is the option to limit which space admins can execute these jobs but in cases where you're trying to empower space admins to manage archiving independently this creates a conflict. In the use case I have, the space admins don't want to have pages archived without them pulling the trigger so even if you were to restrict access and schedule archiving to occur at night this would be problematic.

    Ideally there would be a time control restricting archiving globally or even by space so that space admins still have access but can't trigger a job during the day. I acknowledge this isn't an overwhelming broad use case but it is impactful.

  • 0
    Avatar
    Jay Louvis

    Yes, that was one of the options I found to consider as you mentioned. Certainly is helpful but a more comprehensive restriction on running archive jobs would still be useful. It would help delegate control without relying on a policy for people to follow regarding timing. 

  • 0
    Avatar
    Jay Louvis

    I would also like this feature to make sure jobs can only be run during off hours to limit end user impact. We had an incident with a client where a large archiving job created some database performance issues and we haven't onboarded most of the space administrators to even start archiving yet.

  • 0
    Avatar
    Aron Gombas

    OK, Jay, it is clear now. (I updated the topic title based on this explanation.)

  • 0
    Avatar
    Aron Gombas

    Oh, one more note: did you consider using a "trusted group" for this purpose?

    You could select only a handful people to this group and educate them about the preferred timing and consequences. This feature was built in mind with "not every space admin is equal".

    https://midori-global.com/products/better-content-archiving-for-confluence/server/documentation/configuration#trusted-group

Please sign in to leave a comment.