Here I'll introduce a way to automate site-backups of Jira Cloud and Confluence Cloud with Jira Automation.
(0) Why site-backup is important
Atlassian doesn't officially provide data rollback based on customer requests. So it's essential to take site-backup regularly. For example, the backup will help you when any of site data was lost by the user's operation. Refer to the following part in Data storage FAQ for more details:
Atlassian cloud sites don't support the use of backup data to roll back changes.
Let me clarify what's covered by the approach introduced in this article. It's good as a first step while there are some constraints, such as:
First things first, you always need to have credentials when you do something important:
(1-2) Example - How to encode your API token
$ echo -n "email@example.com:<YOUR_TOKEN_HERE>" | base64
(2) Create a rule for Confluence site-backup
Although you can start with either Jira or Confluence, we'll look into how to configure a rule for Confluence here for convenience.
(2-1) Cron expression
Each backup should be performed after 48 hours interval at least. We here are going to schedule the execution twice a week on Monday and Thursday. Also make sure to avoid maintenance windows of your site. For example, suppose your company sits in EST, specify 9 am in UTC:
0 0 9 ? * 1,4
(2-2) Webhook body
(3) Create a rule for Jira site-backup
I'll put the diff of settings as it's almost same with Confluence.
(3-1) Cron expression
Same here, on Monday and Thursday at 9 am in UTC:
0 0 9 ? * 1,4
(3-2) Webhook body
Other than noted above, there are several points you should be aware of:
Kenta YamamotoAtlassian Team
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events