Hi,
Query 1 - We want to incorporate all documentation related to the team activities into JIRA workflow. Currently our teams are storing their documents outside of Jira, my question is whether Jira is backed up and if so how frequently?
I also searched and found some details in this regard where I could see that Atlassian only creates backups for disaster recovery, which means that these backups are not available to customers. To avoid data loss, it is recommended to make regular backups. If this is the case, how can we make Jira the centralised source of storing all information. Do we need a third party tool for this?
Query 2 -
I have been provided the 'Admin' access but I can not see the fields like workflow, Planning, schemas - How do I see whether I have the Admin rights? Another admins has confirmed that I do have the rights but I do not see the same fields as my colleague (detailed above).
Regards
Priya
Hi Priya - Welcome to the Atlassian Community!
For what you are trying to do, I would say the built in backup functionality of Jira is very inadequate. Like you mentioned, it's more for disaster recovery - it's an all or nothing kind of re-import. You have access to the backup file, but you can't just restore a single issue or project.
For that you would need a third party app like the Revyz Data Manager for Jira app. This gives you the ability to set scheduled daily backups but also the ability to do fractional restores - a single issue for instance or a single project. There are other apps that do similar things out there as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, forgot about the second part. You need to be a Jira Administrator. The term of just "Admin" can mean a lot of things in Jira, such as you might be a Project Admin, which does not have sufficient permissions.
Click on the cog icon in the upper right of the screen in Jira (Settings). If you do not see a section for Jira Settings, then you are not a Jira Admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Priya Ganjoo , and welcome!
In addition to what @John Funk said, you can find out if you have Admin rights by going to https://admin.atlassian.com/ in your browser. If you can get in (you may have to log in with your Atlassian account or via SSO depending on your setup), then you are at least a Jira Admin and should be able to install and manage a 3rd-party app like Revyz Data Manager for Jira (which I also use for JSM). If that's not the case, contact your Site/Org Admin for help. You can search 3rd-party apps in the Atlassian Marketplace to compare features and get pricing, and Revyz and most other Partners offer a free trial for 30 days or so. Good luck!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Is there a space issue within Jira (I do not think we have a premium account) as to how much can we store in JIRA? Our test/regression screenshots are huge so would storing all of them into Jira create a issue with the space?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Priya Ganjoo , as of April 2024: on a Standard plan the default maximum size for a single file is 1 GB. The total storage capacity of a Standard JSM plan is 250 GB. There's an article in the Atlassian Community that may provide more helpful info, https://community.atlassian.com/forums/Jira-Service-Management/How-much-Attachments-can-it-store/qaq-p/2675303.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Priya Ganjoo , welcome to the Atlassian Community,
Queury 1 - ...
You're right... The DR scenario you described is also related to the Shared Responsibility Model, which means that the service provider is responsible for the recoverability and accessibility of its services, and you, as a customer, are responsible for your account data security (including backups and restore).
To ensure backup you can go a few different ways - manually export your data from Jira Cloud (here you can check which Jira data is included in those exports: https://support.atlassian.com/jira-cloud-administration/docs/export-issues/ ) - you can have such backups at any time, but if you need to include attachments, logos and avatars, you will be able to do such backups only with 48 hours gap between them.
Another option is a third-party backup tool, like GitProtect for Jira Cloud (as well as Bitbucket, GitHub, GitLab, and Azure DevOps). With a third-party tool, you can get backup automation, full data coverage, long-time or unlimited retention to keep your backups, restore & DR capabilities like full and granular restore to the same or a new Jira account, your local instance, etc. Here you can find out more: https://marketplace.atlassian.com/apps/1228719/gitprotect-io-for-jira-backup-restore-dr-data-management?hosting=cloud&tab=overview
If you are searching for best practices for building a backup strategy, this article might be at help: https://gitprotect.io/blog/jira-backup-best-practices/
Query 2 - ...
As for the permissions, you might have Project Admin access instead of having Jira System Admin rights. Try to click on Settings (top right), if you don't see Jira Settings, probably you're not a Jira Admin. If you’re missing permissions, ask your Site or Org Admin to review your role under System → Global Permissions.
Regards,
Daria
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.