New in Hutte: Self-hosted GitLab servers, project improvements, and more

You can now “pause” both users and projects in your organization, link your own self-hosted GitLab server to a project, and more!

Link a self-hosted GitLab server to your new project

We’ve added a new option to the project setup flow in Hutte. You can now link a self-hosted GitLab server as your project repository.

All you’ll need is your GitLab access token and your GitLab project URL.

Renaming a project on the setup screen

We’ve added a small quality-of-life improvement to the "Project" setup screen. You can now rename your Project directly on the setup screen, instead of needing to navigate to "Project Settings" first.

See the subscription status of users you’ve invited (Partner plan)

For our users on the Hutte Partner plan, you can now see the current subscription status of the customers that you’ve invited to Hutte. Under your "Invitations" tab, you’ll now see a column called “Plan,” which will show you which Hutte subscription plan each of your invited customers is currently using. If the customer hasn’t accepted your invitation yet, this field will be blank.

“Pausing” a user on your Hutte account

We’ve added the capability to “pause” users on your team instead of deleting them when you want to remove a seat. On your "Org Overview" screen, you’ll be able see your number of active and inactive users at a glance.

You can deactivate (”pause”) a user from your "Members" tab.

Deactivating a user will remove that seat from your billing, and that user won’t be able to log in while their account is deactivated. But their account information will still be saved in the system, so if you ever want to reinstate their seat, you can easily re-activate their account with just a click.

Improved project usage control (Partner and Enterprise Plan)

For our users on the Partner and Enterprise plans, we’ve made a few upgrades to the way that you work with projects.

You can now pause (deactivate) a project. Just navigate to that project’s "Project Settings" screen, and you’ll see the option to deactivate the project at the bottom. This will free up a project slot in your plan, but the deactivated project will be preserved for as long as you need it, and you can re-activate it again with just a click. This is great for projects that might need to go on hold for an extended period of time, but will be picked back up again later.

We’ve also added a project counter to the project dashboard, which allows you to see your current number of active and paused projects.

Choosing which commit SHA to branch out from when creating the first commit on a Sandbox feature

When you’re pulling changes on a new Sandbox feature, Hutte automatically creates your feature branch using the branch name you specified when creating the feature; from the creation or last refresh date of the Sandbox you are using.

But if you do need this level of granular control for your feature, Hutte now allows you to specify the exact point in time in the Git repository that you want to branch out from.

Better error messages after failed Sandbox refresh attempts

We’ve improved the error messages that happen when a Sandbox refresh fails. Previously, we used to show a generic error message when this occurred.

Now, Hutte will show more detailed error messages when a Sandbox refresh fails, giving you more information on the specific cause. This should make the error-causing problem much faster to correctly identify and fix.

Timestamps for a user’s last activity

We’ve added a small improvement to the "Members" tab. There’s a new column labeled “Last activity” where you can see when each member of your organization last performed an action in Hutte.

Fixed date fields bug for certain metadata types

There is a Salesforce bug affecting some metadata types that causes the “Last modified” and “Created date” fields to show the date as January 1st, 1970. We’ve fixed this by having Hutte now detect this bug and hide the date fields when it occurs, to prevent any confusion.

Fixed visual design flaw on "Project Overview" screen

We also fixed a minor visual design flaw that could occur on the "Project Overview" screen in the “Connected Repository” box when the Git Org and default branch names were long.

Explore these improvements firsthand