Hi @Mohamed Saad Taha
From a Jira data protection strategy I would recommend doing the following:
1. Reduce the no. of people who have delete permissions
2. Backup your data on a regular basis
Doing the above reduces your companies risk of data loss significantly - In fact Atlassian recommends that you should back up your data on a regular basis, reference links below:
- Atlassian Security Practices
Reference the 3rd para - "We do not use these backups to revert customer-initiated destructive changes, such as fields overwritten using scripts, or deleted issues, projects, or sites. To avoid data loss, we recommend making regular backups."
- Cloud Security Shared Responsibilities
For implementing #2 you have two choices:
A. Do it yourself (DIY)
B. Use a third party tool
Like anything there are pros and cons for both choices A & B.
We at Revyz have built an automated solution for not only addressing your data protection needs but also address multiple other use cases with our Data Manager for Jira app - Here is a broad overview of the use cases we support:
- Manage | Cloud 2 Cloud data management - more specifically moving configuration and data between sandbox & production - as an example if you have developed a workflow or a screen in your sandbox and you want to move that into production, today you will have to do it manually, with Revyz Data Manager for Jira you can automate that granular copy / cloning of data across cloud sites (of course you can granularly clone data within the same site too ) you can also do a diff of the config before you decide to clone the specific object
- Protect | Jira data protection - You can automatically backup your Jira data everyday and can do the same on an on-demand basis too. More importantly you can restore data in a granular manner i.e. you can restore a single issue (or multiple), an attachment, work flow etc..
- If you want to restore back specific workflows, screens etc.. we support that use case
- Analyze | Jira site analytics - The Revyz Data Manager for Jira provides you the following analytics as of now (more being added)
- Issue Analytics: Who & When stats of issue deletions - This helps you identify quickly what issues where deleted and you can surgically restore those specific issues back
- Attachment Analytics: Finding attachments in Jira is hard, Our attachment analytics pinpoint where exactly attachments are present, what their size & type is. You can slice and dice that information too
- Configuration graph (in beta): Helps admins visualize how the various objects within Jira are connected with each other - As an example you want to find out how many projects are owned by a certain user or how many issue types are shared among projects
- Optimize | Jira site optimization - Over a period of time your Jira site gets complicated and cluttered, you want an easy way to understand what objects are stale / unused and easily delete them, the Revyz Data Manager for Jira provides exactly that information and an easy way to delete unused and stale config, of course what you have deleted is present in the backups, just in case a mistake was made, you can recover them back!
A single app that addresses multiple use cases beyond data protection. Our goals is for the Revyz Data Manager for Jira the Jira admin's tool box over the course of time (a swiss army knife for the admin)
Hope this helps.
Thanks
Vish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.