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.
266 results found
-
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 -
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…
1 vote -
Allow delegated users to edit environment variables
My user is setup on our CI and I have a number of environment variables setup on Custom Labels for ID's.
Whilst this works great the main issue is if I am Sick/On Holiday there is no way for someone else to go in and add/edit the environment variables thus making me a single point of failure/Reference.
What would be great would be either have Environment Variables setup at a CI level and delegated users have the ability to go in and edit/create new ones against the CI (This would ensure only those that know what they are doing are…
6 votes -
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 -
Only notify the Pull-request creator on validation errors
Hi team, not sure if there is a way to do that in the current setup, but I think it would be helpful to add the option to only notify the Pull-request creator/owner on the validation errors, instead of "hardcoding" the email recipients. Regards, Adrian
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.
4 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 -
Enable admin visibility into a Gearset team member's shared orgs
As a Salesforce implementation partner (SI) I have a lot of organizations to manage, well over 50. Each time a new org is added, I can go through and add all the users to that org, but whenever a new person is added to my team, I have to go through each connection and add that user to the list.
As the owner, I would also like to be able to see all the shared orgs inside my account, so I can centrally manage them, rather than just the ones that team members may have added.
1 vote -
Setup using Github Enterprise edition although behind a Proxy
I am running a Github Enterprise edition, but have to configure using custom git setup.
Using the Github Enterprise connection setup, I was able to connect; however cloning the repository failed as the http request to list repositories returns the private host name instead of the proxied one.
Clone functionality works when using the Custom Git link; however it limits our ability to make pull requests and it also requires entry of Username and Password instead of OAuth which is a security concern.
Create a feature which allows the hostname initially entered in Enterprise Setup to be used in favor…
2 votes -
Allow account admins to run reports on their team's usage of Gearset.
I am managing a Gearset account and I need to be able to know who is using Gearset and who isn't so I can more properly assign licenses.
This might be an Enterprise feature, https://app.gearset.com/account/account-report, but really should just be something an account admin can run.
1 vote -
Automate Salesforce org connection on sandbox refresh
When we refresh our sandbox orgs, we have to reconnect the gearset user, would it be possible to use JWT to auto connect to the org?
5 votes -
Make Gearset more responsive via web design
Currently when doing deployments I have realized when i migrate to a smaller screen that gearset isn't super responsive and sometimes i have to drag it back to my larger monitor. This was really highlighted when I was attempting to deploy some metadata from my phone (mac was updating).
Please make gearset more responsive so I can deploy from my phone.3 votes -
Require a Deployment Friendly name
Add option to require a Deployment Friendly name, similar to the current settings to require deployment notes and Jira tickets
3 votes -
Pull Request From Deployment History
Making a pull request via Gearset is only available from the Compare & Deploy Flow.
I'd the link to make a pull request available from deployment history so that users can make the pull request to the various Git/Salesforce environments.
Currently, I am telling my users to note the deployment id for their comparison and hit the link. This appears to work, but isn't user friendly.
https://app.gearset.com/finished?deploymentId={deploymentId}¬ify=true
1 vote -
Show me where the Salesforce Release Changes are in the metadata files.
As a gearset user, I want a guide to the location of metadata components created by Salesforce in each new release so that I don't have to guess and look for the metadata 3 times per year when Salesforce publishes changes to their platform.
Please user your business relationships with product owners at Salesforce to submit this story idea on behalf of clients everywhere.
For example, today I was looking for metadata, if any, created by enabling permission set expiration dates in my sandbox. This won't be availabe in production until release on 10/7 but I was curious if I…1 vote
- Don't see your idea?