New in Hutte: Jira Cloud overhaul, custom success messages, and more
June was a big month for Hutte improvements. We’ve given our Jira Cloud integration a UI and functionality upgrade that will make your Jira/Hutte work a breeze. We’ve also added the ability to create a custom success message for custom buttons, and many more updates that you’ll love.
Jira Cloud integration overhaul and new functionality
Working between Jira and Hutte is now easier than ever. Our Jira Cloud integration now works for Sandbox features and Scratch Orgs alike.
We’ve added a few new features, such as the ability to “lock in” a default Org and the main active features related to the work item.
We’ve added the ability to create a new feature in Hutte directly from the “Issue View” in Jira. This will streamline your workflow and save you some valuable time!
When you create a new Hutte feature from Jira, the name will be pre-populated with a combination of “Issue Reference” and “Issue Title” from the Jira project. Using this default name means that when you later create a pull request for the feature, the issue reference will be continuously passed through, and can be referenced and used by an integration between your Git host and Jira, such as automatically completing your issue when the pull request is merged.
Custom success messages for custom buttons
You can now add a custom success message to a custom button you’ve created in your Hutte.yml. The property is called "success_message." The text is fully customizable, allowing you to include text formatting options and hyperlinks.
You can find and configure your Hutte.yml under “Project Settings”.
Setting a "base branch" for Sandbox features
We’ve introduced the option to set a “base branch” for Sandbox features. When you pull changes on a Sandbox feature, you’ll now see a new “From Git branch” field in the commit information section.
👉
Pulling changes on a Sandbox feature used to automatically branch the feature off from your project’s main Git branch. Now, you can specify the branch from which you want to originate your feature changes before you commit.
By default, this will be set to your project’s main Git branch. But you can easily select a different branch from the dropdown menu.
Show Pool Org status on "Take from Pool” dialogue
We’ve added a small quality-of-life update to Scratch Org creation. When you’re creating a new Scratch Org via the “Take from Pool” option, you can now see the current status of the default Pool Org without needing to expand the drop-down menu. Active Scratch Orgs in your pool will now have a green check mark next to them and say “Active” at the end of the name field.
Show project data on project dashboard
We’ve added more information to the project cards in your project dashboard. For each project, you can now see the number of members in the project in the third line. The fourth line now shows you either the number of active Scratch Orgs in the project (for Scratch Org projects), or the number of active and completed features in the project (for Sandbox projects).
Speed improvements to “All Metadata Browser”
We’ve made some improvements to the way Hutte fetches metadata that should speed up the process drastically, especially when retrieving Apex Classes.
Sandbox Pool: “No refreshes between” bug
We fixed a rare edge-case bug that was causing Sandbox refreshes to occur outside of a blocked window of time instead of inside it, due to a customer’s specific time zone and set time window.
Add column "Created from” on Sandbox list view
We added a new column in the Sandbox list view, labeled “Created from.”
This column indicates which Salesforce Organization each Sandbox was refreshed from. This allows Admin users to have a better understanding of their existing Sandboxes. For example, you’ll be able to see which Org your Pool Orgs are being refreshed from at a glance.
Explore these improvements firsthand
Get in touch with us to discover how we can customize a superior user experience for you!
Harald is the Co-Founder of Hutte, bringing his vision of no-code DevOps to life. His passion enables teams and individuals to focus on what matters most – bringing value to the users they build for.
