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.
1235 results found
-
Provide More Detailed Information on Data Deployment Summary Steps
Currently the data deployment summary displays an elaborate interface but with very little useful information other than record counts. On the right side are Steps, but those steps do not tell the user much. I can see that in one step x records were fetched, for example, and in another step y records were fetched, but I can't see WHY.
Example use case: I had a situation where I was filtering an object but the filter wasn't being honored (more records were being deployed than expected). I could see from the data deployment summary that one of the steps was…
1 vote -
Pipeline automatic back promote
When using pipelines, it would be helpful to have the option to automatically back promote changes through the pipeline. For example, we currently have a CI job that pushes specific changes that admins are allowed to make directly in production into our master branch. We then have a Github Action that automatically merges commits to our master branch to the other branches in the pipeline, so that everything is synced. However, in order to turn on pipeline, we have to turn off our automated merge action, because pipeline creates a bunch of PRs when the automation runs. This forces someone…
5 votes -
Customize CI job commit message
When a CI job pushes changes to source control, it always uses the message "CI deployment from job <CI job name>". It would be very helpful to be able to customize this message.
5 votes -
Add a way so we can easily integrate commits into Salesforce.
What I mean by this is, give users the ability to create and associate commits from in Gearset to a custom Object in Salesforce.
The commit would create a new record in Salesforce, under the custom object, let's call it 'Commits'.
We'd be able to pass through data such as the commit status, the ID of the commit, a link to the commit itself taking us back to Gearset, the name, and author, etc, etc...
I'd imagine this is possible through the use of the BitBucket API, however with SF teams who lack developer resources, this would be a nice…
1 vote -
Revert with one click all changes from this PR
Please allow reverting PR from lower environments. In mine example, we had a feature that went through develop and uat and was waiting in the pipeline to be added to release but the business changed its mind and canceled this whole feature.
Please add an option that with one click we can revert PR and changes from lower environments.
Image:
https://www.dropbox.com/s/ohvymcs16p9n5ge/2022-06-30_14h10_44.png?dl=02 votes -
Include Deployment Name on Continuous integration dashboard
On the Continuous integration dashboard, specifically in the Validation only CI jobs section, there is no way to associate a validation job with the deployment dashboard in Salesforce. We have a validation only job set up to run tests on PRs when they're created. If we get a handful of them all at once, there is a long list of validation jobs running, but we can't tell which one is the one that's actively running. There is no link between the job in gearset and the job in salesforce.
3 votes -
Delete GitHub webhook when the CI job is deleted
When we create a CI job where the source is GitHub, Gearset can automatically create a webhook for us in GitHub.
Would it be possible to delete that webhook in GitHub when we delete the CI job from Gearset? I've got some GitHub repos with failing webhooks due to CI jobs I once created. Obviously, I can tidy up manually from GitHub, but it would be nice to have the option of Gearset doing it for me. The URL seems to be unique to the CI job, so I can't see it having any negative consequences.
3 votes -
Allow for Object Deployments without subcomponents to git
When deploying an object to git currently there is no support to ONLY deploy the object metadata.
We have a large managed package that your code requires the .object file for an object in that managed package to exist for me to deploy fields or other customizations for said object git -> org. When I deploy org -> git to get the .object file into my repo it also grabs all the fields on the managed package object which I don't want/need.
I don't want the fields and I need to specifically get it from the target org because if…4 votes -
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 -
Enable source control as source/target in Data Deployments
It would be great if we could add source control as an option for Data Deployments, this will be useful in cases where we want to backup copies of CPQ record data which manage configurations to our source control repository.
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 -
to let us configure the default metadata filter by deployment pipeline configuration
Can we please have a possibility to configure the "standard" metadata filter by each deployment pipeline project?
I think it is currently preselected by the last used metadata filter from the standard comparison.
As we usually have a specific metadata filter configured by deployment pipeline project, it would be great that we can configure each project with a default one..
Thank you!
2 votes -
allow field level granularity in CI Jobs
Would like the possibly to set up a CI job that only syncs a sub-set of fields on a custom object. For example, we have an org to org sync where we want to update picklist fields but not autonumber fields. Currently we are running this job manually twice a day.
1 vote -
xml formatting support for Illuminated Cloud
I would like to see support in the 'XML quote escaping style' for Illuminted Cloud (and potentially other IDE Vendors)
I am struggling currently as my Admins use gearset for source control commits and my developers use Webstorm and Illuminated Cloud which causes conflicts (generally with the utf/UTF issues but some others as well around validation rules and some formula fields).
Ideally, If a team standardizes around one IDE then all they have to do is come in to that setting and set it to what the IDE does as a default and then you wouldn't get any conflicts with…6 votes -
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 -
Possibility to validate a feature branch as a whole without having to select the Metadata type
It looks like the current validation jobs setup in Gearset needs the Metadata Type to be explicitly selected to perform the validation. This should ideally be optional and there should be a capability to just validate everything that is there in the feature branch against the target org. It's really annoying for us that we have to select the Metadata Types to be validated.
2 votes -
Prevent deployed validated packages from being deployed subsequent times
Currently, after you deploy a validated package it no longer appears under the Validated Packages menu, however, if you still have the link for the validated package and navigate to that package it doesn't give you any indication that the package has already been deployed and allows the user to click the Deploy button again, assuming they have deploy permissions on the target org connection.
As part of our production deployment approval process, we store the link to the validated package in our external ticketing system (https://app.gearset.com/validated-package-details?deployPackageId=<package id here>). When completing the ticket, users use that link to…
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
- Don't see your idea?