Currently, users can select metadata components to commit to Git. This project will improve the preview and enable selective committing of specific parts of the differences (diff) between the metadata in the Sandbox and the Git repository.

This module will answer the question: “Where is my feature in the release pipeline?” It will integrate with Git, will support various release workflows, will provide real-time tracking, and will come with a user-friendly visualization.

We implement several enhancements, including the ability to pause users and projects, and improved feedback on the cost implications of adding more users.

Our v1 of the Hutte Packaging Module allows building 2nd Gen (Un)Managed Package versions, and to install them to target orgs. We want to further improve this functionality, based on the User Feedback we have received.

This supports use cases such as adding business users for convenient acceptance testing in Sandboxes or Scratch Orgs.

Provide a frontend to SFDMU

Currently, the Hutte CLI exposes selected functionalities of Hutte, such as taking a Scratch Org from the Pool, as an SFDX Plugin. We aim to add more commands to enhance developer productivity and to support integrations.

Enable control of all project settings, such as pool settings and default Scratch Org shape, through code using a configuration file, like Hutte.yml.

Leverage LLM to enhance user efficiency in debugging failed deployments and extracting relevant information from pipeline results.

Currently, scripts from Hutte.yml run in a Docker Image maintained by Hutte, which fulfills all pre-conditions for typical Salesforce automation. However, some customers might have additional requirements to customize the runtime environment.

Facilitate work in Development Environments (Sandboxes, Scratch Orgs) with different users, in order to support developing and QAing role-dependent features.

Rather directing users to the connected Git Host in order to consume reviewers feedback and check the build state of their PR, this information should flow back into Hutte and be reflected on the UI.

At present, Hutte offers various standard settings for selecting tests to run during deployment. We aim to include a smart pre-selection of tests based on the Metadata of the deployment.

A Dashboard to present relevant DevOps metrics like average Scratch Org creation time, Dev Hub Health, Number of PRs created. It should support measuring performance and gaining insights on the ALM of Salesforce projects.

Implement optimizations like scheduled refreshes for Scratch Org Pools, multiple Pools in one Project etc.

Keep track of changes like Salesforce Connection changes, renaming Scratch Orgs or Features etc.

Open Hutte up for custom integrations by exposing Webhooks, which allow subscribing to certain events happening in Hutte.

Define presets of Profile, Permission Sets and License in Hutte and create additional users for your development environment (Scratch Org or Sandbox) from there. This facilitates testing your project in different roles.

We want to move away from an Org centric to a Work centric model: No matter if Sandbox Feature or Scratch Org, we want to enhance "Work Items" by description, status (and potentially further fields known from ALM- or Issue Tracking Tools)

Open up the Hutte GraphQl API for customers to allow the creation of custom integrations.

Add commenting or chat functionality to the "work item" (Scratch Org, Sandbox Feature) view.

Also referred to back promotion or "refresh Org Metadata". Similar to existing "refresh" functionality for Scratch Orgs. Already relatively easy to implement with custom buttons, we might want to make this standard functionality.

Improve access by supporting sign-up and sign-in with Salesforce, Google and potentially other Providers.

Build out a more granular way to manage roles and permissions on organization and project level.

We will significantly improve the user experience after signing up for Hutte, making it easier to derive value from using the platform.

This is useful if the auth token from Production can't be used as the Sandbox has been created by a different user than the one used to connect Hutte to Salesforce.

Make custom actions launched from custom buttons configurable, by allowing users to pass values through an input form which opens upon click of the custom button, if the respective configuration contains variables.

Hutte Jira Plugins for Data Center and Cloud link Jira Issues to the respective Scratch Orgs in Hutte. A next iteration should include Sandbox Features, as well as the creation of Sandbox Features and Scratch Orgs directly from Jira.

Hutte maintains a growing number of recipes which customers can use to power their Hutte Developer Experience, as well as their CI/CD automation. Those are available on GitHub, GitLab, Bitbucket and Azure, and will be made accessible through our UI.

Hutte Sandbox Projects have a simple deploy feature, which allows shipping the changed Metadata from a single feature to Production. We want to add multiple Orgs as potential deployment targets, and improve the deployment capabilities (e.g.validation).

Add more functionality and improve the UI by grouping Metadata by type, visualizing .forceignored-files, allowing the creation of Draft PRs, as well as supporting commits without PR.

Improve the "Invite Users" functionality by providing a handy UI for inviting multiple users at once and selecting appropriate project access and role.

Additionally to support connecting to repositories hosted on GitLab Cloud, we add support for GitLab On-Premise Edition.

dx@scale is a powerful Open Source Toolkit for building and maintaining an enterprise, package based Salesforce ALM. Hutte should be usable as its UI, closing the gap between DevOps Teams and Admins/low-code/pro-code Developers.

Improve user experience by adding features like for example favorites, adjustable columns and inline editing.

Efficiently manage and provide fresh Development Sandboxes for feature development.