Revyz Configuration Manager for Jira Capabilities
Capability | Revyz Data Manager for Jira |
Information Security & Compliance | |
Encryption | Data is Encrypted in-motion and at-rest In-Motion | TLS 1.2 At-Rest | AES 256 bit key, AES-GCM mode, HKDF-512 bit key derivation and commitment, ECDSA with P-384 and SHA-384 More information here - https://support.revyz.io/legal-security/revyz-security-compliance-overview |
Qualys SSL Labs | A+ https://www.ssllabs.com/ssltest/analyze.html?d=jira-app.revyz.io |
SOC 2 | Revyz is a SOC2 Type 2 compliant organization check out our Trust Center for more information - https://trust.revyz.io |
ISO 27001 | Revyz is a SOC2 Type 2 certified - ISO 27001 certification is driven by customer needs and it is currently gathering interest! |
Personal Information Treatment | Revyz Configuration Manager app does not access a customers personal information and neither does it process that information. |
Immutable App Audit Logs | The Revyz App maintains a detailed access log of administrators accessing the Revyz app as well as maintaining any actions taken with the app including app setting changes, data restores etc.. |
Role Based Access Control | The Revyz App utilizes Atlassian native roles based access control scheme |
Data Residency | 🌐 Data Residency options: AWS US East 🇺🇸 Frankfurt 🇩🇪 Sydney 🇦🇺 Canada Central 🇨🇦 Singapore 🇸🇬 Reference data residency support - https://support.revyz.io/legal-security/data-residency |
Immutable, air-gapped backups |
|
Support | |
Support Operations time & process | We have customers across the globe - hence we offer 24x5 support during weekdays, we are just a zoom call away! The Revyz team operates out of 3 countries:
To request a call at anytime reach out to our support desk here - https://revyz.atlassian.net/servicedesk/customer/portal/1 someone will respond to schedule a zoom meeting if need be |
Phone Support |
|
Data Protection (Backup & Restore) | |
Easy setup | Native to Atlassian App installation process - you never have to go outside of your Jira console |
Automatic configuration backups - 3 times weekly |
|
On-Demand backups of configuration |
|
30 day backup retention of configuration |
|
On-demand restores |
|
Granular/item-level restores |
|
Detailed backup analytics and logs |
|
Supported items | As Supported by Atlassian API's - See detailed list below |
Configuration Management | |
Configuration Rollback |
|
Configuration Diff |
|
Sandbox to Production (Cross-site) Data Transfer |
|
Jira Site Analytics | |
Issue Deletion Log | A very critical feature - Enables the admin to understand who is deleting what and when |
Jira Site Summary |
|
Jira Site Optimization | |
Configuration Usage Analysis |
|
Bulk Configuration Deletion |
|
Accidental config deletion prevention | Check to see if a config object is present in your backup before deleting |
Log of all deletion actions |
|
Additional Features | |
Detailed Error Logging |
|
Notifications via Jira Project integration (Email / Slack / Teams) |
|
Free plan | We do not offer a free plan at this point of time, although we offer a free trial which ranges between 30 - 59 days and is extendable on a case by case basis |
Jira Object Support | |||
Projects | Backup | Restore | Comments |
Projects |
|
| |
Project categories |
|
| |
Project components |
|
| |
Project features |
|
| Only for Software projects. JSM is not supported due to API limitations |
Project versions |
|
| |
Filters |
|
| |
Dashboard | Roadmap | Roadmap | Gathering Interest |
Project properties |
|
| Backup runtime consideration |
Project property keys |
|
| Backup runtime consideration |
Project avatars |
|
| Backup runtime consideration |
Configuration Objects | Backup | Restore | Comments |
Issue types (Epics, Story etc) |
|
| |
Sub tasks |
|
| |
Issue type screen schemes |
|
| |
Issue link types |
|
| |
Boards |
|
| |
Sprints |
|
| |
Workflows |
|
| |
Workflow schemes |
|
| |
Workflow scheme drafts |
|
| |
Workflow schemes project associations |
|
| |
Workflow transition properties |
|
| |
Screens |
|
| |
Screen schemes |
|
| |
Issue type screen schemes |
|
| |
Screen tabs |
|
| |
Screen tab fields |
|
| |
System Fields |
|
| System fields cannot be overwritten |
Custom fields |
|
| |
Field configurations |
|
| |
Field configuration Scheme |
|
| |
Issue attributes and features | Backup | Restore | Comments |
Status(s) |
|
| |
Resolutions | In Development | In Development | |
Priorities |
|
| |
Issue security schemes |
| In Development | |
Notification schemes |
| In Development | |
Permission schemes | In Development | In Development | |
Issue linking |
|
| |
Issue properties |
|
| Backup runtime consideration |
Issue property keys |
|
| Backup runtime consideration |
Issue remote links | Roadmap | Roadmap | Gathering Interest |
Security | Backup | Restore | Comments |
Project roles | In Development | In Development | In Development |
Permission types |
|
| Types are created by default |
Jira Service Management | Backup | Restore | Comments |
Service Desks (as Projects) |
|
| |
Requests (as Issues) |
|
| |
Request Type |
|
| |
Request Type / Portal Groups |
|
| API Limitations |
Form Templates | In Development | In Development | In Development |
Service Desk Queues | Roadmap | Roadmap | Gathering Interest |
Organization | Roadmap | Roadmap | Gathering Interest |
Customers | Roadmap | Roadmap | Gathering Interest |
Additional | Backup | Restore | Comments |
Automation Rules |
|
| Restore is manual at this point of time, we would love your feedback |
Advance Roadmap | Roadmap | Roadmap | Gathering Interest |
Third party app data is not backed-up as that data is not available in Atlassian Cloud. Our app is dependent on the API’s that are published by Atlassian. Thus far no other third-party app vendor has been open to providing a mechanism for backing & restoring up third party app data that is stored in their own cloud. | |||
