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.
1361 results found
-
Rename the Name bar in compare and deploy to : Name (api)
Simple to implement, just a string rename...
Rename the Name bar in compare and deploy to : Name (api)
It would show clearly that the name displayed there is the API name, not the "label" name XD
Cheerio2 votes -
Allow the creation of CI Jobs against Salesforce orgs that we are delegated to, instead of needing to be owner.
We have 2 admins that we want to be able to create all of the CI and Pipeline Jobs, even if they don't have their own credentials in a particular Salesforce org. They have Deployment delegation, and can run compare and deploys, but not set up integration jobs.
This is then requiring us to either, provision extra licenses in each sandbox for our DevOps administrator, or have the developers create the CI jobs, which they are not comfortable with.
And, as we start the Pipeline Pilot, we would like to leverage all of the existing CI jobs, but, that is…5 votes -
Provide output from Gearset during the validation in terms of what tests were being run
I had unit testing jobs running ALL tests in source (full sandbox) and target (production) org - resulting in 80% and 79% test coverage. However, when I started to deploy my changes - the validation failed because test coverage was only 74%. Finally, after a few days, I figured it out.
I was just simply clicking "Validate" (i.e., did not choose specific tests). In the past - that ran "all tests". But something seems to have changed. When I picked "choose tests", about half the tests in my org were "automatically selected". I manually selected all other tests - effectively…
1 vote -
Add option to make picklist fields non-restricted before performing a data deployment
Similar to being able to disable validation before performing a data deployment it would be very useful if there was an option to automatically uncheck the "Restrict picklist to the values defined in the value set" option for some or all of the picklist fields in a deployment.
We have data that includes picklist values that are no longer active this causes errors on individual records as part of the load. Currently I have to pick through all the errors manually then uncheck the option for the corresponding picklists fields on the target org. Then after performing the deployment I…
4 votes -
Ability to mark certain branches as your favorite branch so you can pick them quickly
When selecting a branch from source control, it would be great if Gearset had an ability to mark certain branches as favorites so they appear the top of branch selection dropdown.
3 votes -
sfdx repo deployment should be in subcomponents
Context: Compare and Deploy from Org to a Repo.
as i understand it, even if my repo is in SFDX format (Object subcomponents), Gearset still does the compare in the metadata format.
it reads the components from sfdx, combines into a .object form, and then applies the changes to the .object file and then decomposes again.this is causing unintentional changes to be part of our PR
2 votes -
Enhance Metadata Filter Type Recognition
Our team has struggled learning the Metadata API names of metadata types when compared to what items are called in change sets. One example would be to highlight Weblink when a user searches for Button.
3 votes -
Allow users to create customized list views on the deployment history tab
It would be immensely helpful for our team, that works across dozens of production orgs and sandboxes, to be able to create deployment history filters (or list views like in Salesforce) that support filtering based on an org's mydomain, the username's domain, or the Gearset user that facilitated the deployment.
1 vote -
Offer the ability to set the ignorewarnings flag on an individual "Compare and Deploy" basis.
Would like to see the ability to set the IgnoreWarnings as an override for an individual Compare and deploy, in addition to at the global level. Occasionally, we will do a community deploy, for example, that returns a warning about a page that includes a Dashboard component, with the warning that the Dashboard ID or the Filter ID might not exist in the target environment. Once we see those errors in the validation results, it would be convenient to rerun the deploy, and ignore those warnings. Possibly similar to how the Test execution options are set on the Deploy button…
3 votes -
CI Job Email Notification with PR info
We do receive an email notification when CI job is deployed. Is it possible to know which PR is deployed with that CI Job? Now, the email notification only has the info with branch name, source, target and deployment summary. it'll be great if we can know the PR name that is associated with this CI job, some users, like QA team, will receive emails and know the PR with card info is deployed so they are ready to test. thanks
1 vote -
Data backup history log export
I would like to have the option to export a data backup history log for a specific period of time. E.g. for the last 60 days export in CSV or xls format following data:
Started, Last updated, Status, Duration, Changed, New, Deleted.For internal and external audits we are required to provide a list of backup jobs run in specific periods with details.
1 vote -
Move Failed Tests before Passed Tests when deployment Fails
Hi,
I would love to see the Failed tests to be listed above the Passed tests in case deployment fails.
Right now User has to always scroll down at the list (as you are usually not interested on what has Passed rather what Failed).
Also this shouold be super simple to implement :)
Thank you & keep up the good work,
Cheers,
O.1 vote -
Gearset Scratch Orgs: Generate Passwords
Our team would like an enhancement to how Gearset handles generating scratch orgs from authorized Dev Hubs. We want to be able to provide log-in credentials to non-gearset users in order for them to use these scratch orgs and perform development work.
We want our deployment manager (gearset user) to manage the provisioning of scratch orgs and the retrieval of changes in these orgs to source control. Our developers currently just focus on developing features and are abstracted from the complexities of the deployment process.
To make this process a lot simpler for our deployment managers, it would great to…
2 votes -
Granular "difference types to deploy" on a metadata level
In the CI job, we would like to have the ability to specify on a metadata level if we want to deploy new items, update items and delete items. There are examples of metadata where we always want to delete and others where we don't want to.
2 votes -
Add deployment job detail info (such as date/time) at the header in the detail view
I have a markup screenshot for the above feedback but I don't find a way to add attachment here.
1 vote -
Add ability to deploy ObjectTerritory2Association object
The ObjectTerritory2Association object does not get populated in the target org for accounts that are manually assigned to territories. This object is used by Territory Management 2.0 and holds the association between accounts and territories. After the deployment, I can see that this bridge object did get populated with the territory linkage for accounts that are automatically assigned to territories. This is expected because an insert of a new account with proper firmographic information will result in the account getting tagged to the correct territory (i.e. if the Account’s “Exclude From Territory” flag is not set to True).
However, there…1 vote -
Filter Deployment History by Source / Destination
At this time, there does not appear to filter deployment history by specific orgs AND other criteria in the general "filter" text box. I would like to find specific packages deployed to a specific org and also that have a standard friendly name. I am only able to enter text to filter by the friendly name and the additional filters allow for source / destination type, but it does not allow for specific source / destination.
2 votes -
Add additional deployed packages
When combining packages for a deployment to a new source, it would be helpful if I could add additional packages to a comparison. There are times when I realize a package or two may have been missed in the original combination, and when reviewing the missing components, I realize a missed another deployed package. Without the ability to add additional packages to the comparison, I must start the combination of packages all over again.
1 vote -
Select All Option in Deployment history
It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.
2 votesThis is now possible as long as a filter is applied to the deployment history page.
-
Send email alert when monitoring job fails
It would be helpful if Gearset would notify the user when connection problems cause a monitoring job to fail.
For example, if the error "Error while getting access token due to expired access" occurs, Gearset could send an email to the author of the monitoring job informing them of the problem.
3 votes
- Don't see your idea?