Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
231 results found
-
Incorporate Relationship Graph into metadata deployment
Right now is it not possible to deploy Relationship Graph metadata according to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_relationshipgraphdefinition.htm with Gearset. This metadata is required for the so called Actionable Relationship Center, which is part of Financial Services Cloud. Even though the meta data is available in the Vlocity filter in Gearset, the items we are looking for doesn't fall under that one. If selected, no meta data get retrieved and therefore no deployment happens.
6 votes -
Write Deployment Results back to the user's Salesforce org
When setting up a deployment, it would be helpful to capture Deployment Results in a custom object in the running user's Salesforce org. Users would be able to specify a unique reference at the point of deployment, which would track through to the Salesforce org.
Information about the deployment would be captured in a Master record, with data about individual components existing in Detail records.
Org admins would then be free to leverage automation features to map the created records as they see fit.
As a consultancy that tracks our customer requirements in Salesforce, our use case would be that…
14 votes -
Release Branches
If I create a Release Branch from UAT, I no longer need all the individual Feature branches.
Inspired by Gitflow and the current Gearset Expanded Branching Model.
Currently: The Expanded Branching Model will create a Feature Branch PR to main for every Feature branch that is merged to UAT branch.
Desired: When I create a Release branch from the UAT branch, then Gearset should close all the current Feature Branch PRs to Main Branch - if and only if the Feature branch was already merged to the UAT branch.
This is related to branch pattern matching because…
2 votes -
Add schedule deployment for Pipelines
It would be great to add a new feature to cherry pick and schedule deployment for the changes that have reached up till staging/uat and should be released to Prod. Without this feature it becomes difficult to manage releases to avoid downtime.
6 votes -
Link to the Salesforce Validation in Progress from the Pipeline
When I deploy using the standard deploy interface, there is a link that allows me to view the deploy progress in Salesforce.
In pipelines, I would like this same feature. When a deploy has been running for a while, it's useful to know where it is in the process and a quick link would be quite nice.
2 votes -
link deployment to a salesforce case
The ability to link a Gearset deployment to a salesforce case record. If an org uses cases to track a bug or feature, this feature would close the loop from that case to the gearset deployment.
I understand that there is a post to chatter functionality but it would be nice to target a specific case for auditing purposes.
1 vote -
Yellow help icon
i love the help you guys provide, really great.
Suggestion.. The yellow circle that you open and drop down.
1) can you move it to the header, and if there is a pending message show the yellow circle with a number in it ( number is count of pending messages )
2) can you make it a separate window model? typically when i am chatting, i need to see the entire screen and the current pinned model is usually in the way and i need to click the arrow to get rid of it.
If i could drag the window…1 vote -
Ability to turn rules/processes off as needed with ability to rollback
There are times when need to update data or load data into Salesforce org and need to turn off rules or processes before updating data or loading the data. When doing a data deployment, GearSet has this ability, and I would like to have this ability to do this without a data deployment. Ability to turn off Validation Rules, Required Fields, Restricted Picklist, Workflow Rules, Flows/Process Builders, and Triggers one by one or turn off all. Then roll back once finished updates.
1 vote -
Introduce Import/Export feature for Custom Filters
Expose the underlying JSON/XML for Custom Filters so that we can export it, modify it in a text editor either by hand or with python scripts, then load it back into the custom filter.
For example I have my main CI filter with 50ish metadata types, and every other filter is a subset which I establish by cloning the "master" filter and deselecting metadata types. Whenever I make a change to the master filter I am forced to nuke all the the "detail" filters and recreate them off the master using the above approach.
So many clicks. My preference would…
9 votes -
support blank values and/or regex in the "Find What" field on Environment Variables
...support blank values and/or regex in the "Find What" field on Environment Variables.
I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.
3 votes -
Allow me to configure my default landing page on logging in
Specifically, I use the Pipelines most of the time and would love for that to be there as soon as I login. While my use case is Pipelines specific, I would guess that others might want a different page when they login, so it would be nice to be able to configure this on a per-account basis.
7 votes -
Provide and enforce branch naming conventions
Branches get all kinds of really stupid names over time. It would be nice if Gearset provided an option to template new branch names. For example when my users need to create a new feature branch for their user story, Gearset should prefix that branch with 'feature/'. When a release branch is created it should be prefixed as 'release/'. Bugfixes or Hotfixes could be bugfix/ or hotfix/.
Dictating naming conventions is unenforcable. Keeping branch names organized goes a long way to keeping the repository maintainable over long periods of time. Even if folks are well intentioned, git branches are case…
1 vote -
Send Email when a package is Validated successfully with PDF of Deployment Summary.
We currently receive an email with deployment summary as PDF attachment after successful deployment, but we also want this feature for successful manual validation. This is help us review the validated package summary with Deployment approval teams in our ORG.
2 votes -
Enable a consistent, buildable set of Metadata for Releases
I'd like to have a way to work with a consistent set of metadata items for a release, that I can add, remove etc, and consistently deploy into a variety of sandboxes and ultimately Production.
Currently, if you clone a previous deploy, items are de-selected if they're the same between the environments being compared. That means once I've deployed, I can’t ever get that “list” of items back and I have to rebuild it every time.
A likely scenario is that I've deployed some metadata from Sandbox A -> B. Lets say it's 5 Apex classes. I then realize that…
1 vote -
language
Gearset UI Language specification. Allow users to specify which language they want the UI presented in and then show the correctly translated terms in that language. When using google to translate the UI the words it chooses are not always relevant.
1 vote -
Make Pipelines a Top-Level Menu Item
This is a less-good, but arguably easier to implement, version of my request for customizable landing pages. It takes a few clicks to get to pipelines and, since it's the place I live most often inside of Gearset these days, I'd love it if it was a menu option that is parallel to "Continuous Integration" so I could get there in fewer clicks.
5 votes -
Create a pop-up warning when on the Selected Items tab before you can deselect all items
Without the Undo feature, there is the odd time (nightmare situation) where you haven't saved your compare and are on the Selected Items tab and accidentally deselect all items. It would be great to get warned that all work will be lost unless it's saved or the deselect action is canceled.
3 votes -
Allow Filters to be Customised in Pipelines UI
Currently, you can create new filters in Compare & Deploy, but when you are comparing and deploying from within the Pipelines UI on your development org, you can only select existing ones. This either means you have to get your team to go into standard Compare & Deploy to set up specific filters first, or they always have to select the filter that includes everything.
1 vote -
Change language to focus less on Source Controls and be more user friendly
Gearset is great for non-technical users or those that find Source Control daunting. However, the terminology used in Source Control has leaked over to Gearset, and I think this detracts from the useful aspects of it, and at times just makes it feel like an extension of Source Control.
e.g. "Create Pull Request" in the Pipeline UI should be labelled something more friendly like "Request Feature Deployment"1 vote -
Hide the "Create Pull Request" button on Deployment Success Screen
Currently, we are setting our team up to use Pipelines, which has the benefit of guiding users down the pipeline in the right way (they can't create a pull request from a qa branch straight to main without going to uat for example). However, when they perform a commit from an org to a feature branch, the Deployment Success (commit success) screen has a button that allows them to create a Pull Request directly to any branch that they want. There should be an option to hide this from users, especially given the benefit of only being able to move…
1 vote
- Don't see your idea?