Automated backup supported or not

[Aaron Hicks]

Some pages say the automated/automatic backup/export scripting is not supported, other pages say it is, can this page be updated to be more specific please?

Since I could not comment on an answer to the question below(comment editor never completes loading), I updated the question.

Please refer to https://confluence.atlassian.com/jirakb/removal-of-webdav-directory-support-for-jira-cloud-instances-859477758.html

When you click at the bottom to see questions on that page you will see this question - Hence the number 859477758 in the tag for this question. it associates it to that page. My question relates to that page. (It links from page to question but there seems to be no way to link from question back to page?)

At the time of writing this page states: "Automated exports for backing up your data
JIRA Cloud has supported automatic backup file creation and download via a private API and the automatic-cloud-backup script from Atlassian Labs. We have made changes to this script to support the new JIRA Cloud backup mechanism. To continue creating automatic backups, download the updated script from Bitbucket."

This paragraph includes the phrases "Automated exports for backing up your data" and "automatic backup file creation" and "automatic-cloud-backup script" and "automatic backups".. My words "automated backup" refer to these phrases.

It is clear that Atlassian supports the underlying mechanism for doing exports. It is also clear that the sample scripts for using the API for accessing it is not directly supported by Atlassian. In places the API is referred to as "private" and I could not find API reference documentation. What is unclear is whether the API exposed by Atlassian for such exports is a formal public API that is documented and supported. Can people make plans with the assumption the API will remain and be supported or are we at risk that the API is experimental and might be discontinued?

My question is whether what this page and this paragraph refers to is supported by Atlassian or experimental. This page implies it is formally supported when it says "JIRA Cloud has supported automatic backup file creation and download via ...",

My request is that you update the documentation to remove ambiguity as to what is a formally supported and documented feature and what is experimental and used at customer's own risk.

Regards

Ruan

[Walter Buggenhout · Accepted solution]

Hi Dima,

Portfolio is designed to help you answer the question 'when you will be able to deliver a given amount of work' in a confident manner. Behind this question are 3 classic PM concepts: scope, resources and time.

When you connect JIRA data with a new Portfolio plan, Portfolio tries to populate these three concepts with data it can deduct from JIRA. Teams (you resources), are a concept that does not formally exist in JIRA, but it is the group of people that actually participates in order to get the work items on your boards/filters/projects done. A team is created in your Portfolio to help you manage the resource part of your plan better.

If you want to know more about how this works, spend 30 minutes of your time to watch the demo videos. You can find them over here:

https://www.atlassian.com/software/jira/portfolio/demo

There is a specific 4 minute video on there dedicated to managing teams specifically.

Good luck and happy planning! 

[dima]

Thank you Walter for your answer and the helpful demo. I think now I understand the teams concept better and how to apply in the Portfolio plans.