August 2024 Update: UX… we did it! GitProtect 1.8.0 introduces a completely NEW onboarding experience
Last Updated on August 13, 2024
Welcome to our post-release blog post where we share the latest GitProtect enhancements and new features launched with version 1.8.0. Although we believe that these changes could not have been missed!
Welcome onboard – a completely NEW onboarding experience
If you are not yet our customer, or you want to test GitProtect in the field again – get ready for some big changes! When logging in for the first time, you will be immediately directed to a new screen presenting all possible resources to secure with GitProtect. By default, you can connect a service with GitProtect within the literal 3-step process. However, if the your company requires authorization using login, token, or GitHub App – access them in the advanced mode aside.
UX… we did it!
Although the process was created with new users in mind, we couldn’t forget about those of you who already use GitProtect – our prominent, loyal customers.
We have made it easier to add new organizations or secure more resources. Because, as you probably know, we are constantly expanding our solution to protect more data and more platforms with Azure DevOps first to come. But more on that later…
Now check out what’s waiting for you in the app today!
Context menu
After logging in, you probably noticed that the upper blue bar, which contains the context menu for the currently visible subpage, has also undergone visible changes. Now setting up a new backup plan or adding new services to protect is faster and easier. We have also moved the language setting to the User’s action and provided an easy way to upgrade or purchase licenses.
Backup plan configuration – little change, huge difference
Finally! From v. 1.8.0 you start defining new backup plan with choosing a platform you want to protect – GitHub, GitLab, Bitbucket or Jira backup plan. A simple change, logical arrangement, and such a convenience! It’s one of those little changes that make a huge difference.
Default enryption key brings new security level
To increase the security of user data, encryption is enabled by default for each new backup plan. For this purpose, a default encryption key is generated, which can be viewed only once at the time of its creation.
GitHub Classic Projects to V2 Projects auto-converter
As you probably know, GitHub support for classic projects ends on August 23, 2024. For this reason, as part of version 1.8.0, we have introduced a mechanism for auto-converting classic projects to V2 projects. If your current backup copy consists of classic projects, during a restore process these projects are going to be converted to the V2 type and you will be notified in the restore task summary.
Faster, more efficient, more friendly. In one word – IMPROVED!
It’s not over yet! Version 1.8.0 introduces many improvements to enhance the speed, efficiency and performance of our software. Here are some of them:
Optimized performance during Jira Granular Restore
Version 1.8.0 brings more optimizations within the Jira Granular Restore process. This time we focused on optimizing incremental backups with granular restore enabled.
Improved configuration of additional accounts in the GitHub, Bitbucket, and GitLab organizations
We have noticed that some of our users only partially configure the throttling mechanism for the git organizations and adding additional accounts or GitHub App. Hence, we decided to include within the configuration process information to edit the backup plan next. To benefit from adding additional accounts enable sharing tasks between many credentials in advanced backup plan settings.
SaaS Service autoscaling
No more RAM limitations in SaaS services! From this release, when RAM limit is not enough to perform the operation, the service will automatically send a request which, after our approval, will assign more resources.
SLA reports notification on your Slack
GitProtect 1.8.0 provides a new type of Slack notification – SLA report is ready to download. We want you to stay up to date, however convenient for you.
Time zone support in backup plans
Another improvement in this release is the addition of time zone support in backup plans. From now on, you can set the time zone in a backup plan schedule. Of course, changes from summer to winter time and vice versa have also been taken into account – no more changing schedules during each shift!
Other improvements
- Support for the GitHub merge settings
- Restore of GitHub outside collaborators metadata from a backup copy
- Restore of Bitbucket repository details from a backup copy
- & more.
Full changelog available here.
