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 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.

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.

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.

Provide a frontend to SFDMU

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.

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.

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

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

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

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.

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

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

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.

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.

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.

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.

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

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

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

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

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