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.
1240 results found
-
Enhance capabilities around 'co-administration'
In our organization we have a couple different salesforce admins that are administrating the salesforce development pipeline in which several developers are making changes and deploying them via gearset. Right now it seems cumbersome/duplicative to do this particularly around the area of adding a sandbox org and then managing permissions of the developers to that sandbox. It would be nice if there was a way for one admin to connect the sandbox, grant the other admin "Owner-level" access to it, and for the two admins to have a shared view of the user access to that org, so I can…
2 votes -
Create a Master-Switch Only deployment process
Can you create a master-switch deployment option? It would be similar to how this operates: https://sfswitch.herokuapp.com/
The issue is that this master switch does not always work with managed packages in production orgs.
So a way to automate the turning off/on of Validation Rules, Process Builders, Flows, and Triggers.
Use Case: We are building a new app and have significant data migration to do. It would help to have a master switch to turn off processes in PROD, deploy date, then, flip the master switch back to turning processes back on.
2 votes -
I have so many connections and jobs, is it possible to have group them (in future release?)
I have so many connections and jobs, is it possible to have group them (in future release?)
2 votes -
Allow (restricted) editing of source XML to add deployable properties that can't be fetched via Metadata API
Example:
It is impossible with OOTB Gearset to deploy an autonumber field with a starting number and optional populate existing rows. Why? Because the SFDC Metadata API as of V42 doesn't allow fetching of these two properties of the CustomField object:<populateExistingRows>true</populateExistingRows>
<startingNumber>1</startingNumber>Once in source, they'll deploy just fine to the target org. Note that changesets support this feature.
The workaround, which is to deploy to target branch and then edit target branch is sort-of-OK but it would be nice to modify this in the source. Of course, if you Refreshed Comparison, your edits would be…
2 votes -
Deploy parts of Settings
It would be nice if you broke up the settings into smaller subcomponents. For example the Security settings would be more useful if you extract out the password policy changes so we can pick and choose what Security settings we need. I thought of this concept similar to how you break up profiles into sub component. This could get noisey in the list of changes so an alternative to that could be to bundle it under components like how CustomObjects work.
2 votes -
Add a note against individual components in a draft deployment
While comparing two Org's for differences and saving the 'Draft deployment':
Files that I'm sure and fine with the differences and happy - so tick them.
Files that are important to be deployed but I am yet to discuss those differences with some peers from team (dev / support). I would like to mark these (or / and) comment against these - with some useful notes (ex: impact or risk analysis related notes). Once these are discussed, I can then tick them - indicating I am happy to deploy these.
Once I mark the files as either 1 or 2…
2 votes -
Ability to manually hide/filter component differences by single flag
When reviewing comparisons it would be extremely helpful to have the ability to manually 'hide' a component difference (e.g. a single flag to filter out, ignore, or even 'grey' a component differences) once you have a) reviewed the XML and b) determined you do not want to deploy or view that component in a saved draft. I.e. a third state that is not simply 'selected' or 'deselected'.
Current filters by component type, name, et al. don't accommodate for wanting to hide a known component difference (e.g. like an Apex class still under development) so that you can only see remaining…
2 votes -
Reuse Deployment Package (clone) should use sticky "Source Repository"
Use case:
1. Compare and deploy from repo-R/master to org A
2. Clone deployment from repo-R/master to org BUnfortunately, when the clone deployment displays the dialog "Reuse Deployment Package"...
a) When you select GitHub, the dialog doesn't default the repository to Repo-R but instead displays a picklist of all possible repos the running user has access to (in our case that is 100+)
b) Better would be to remember in cookie the repo the developer last used and default to that choice so scrolling through 100 items is not necessary.2 votes -
Allow renaming of picklist values instead of creating new and deactivating
Currently, when you rename existing picklist values in the source org (including renaming the API name of that value), Gearset will deploy this to the target org as a new picklist value and deactivate the old value. This means we have to manually delete the value in the target org and specify which value to use to replace on existing records.
It would be great if Gearset could give the option to map a picklist value in the source to a picklist value in the target and allow a rename of the value in the target.
2 votes -
Show filtered counts on the results grid tab titles
When comparing two orgs. We need to show the eaxact number in the Tabs(Changed Items, New Items) when filtered.
2 votes -
Provide link from standard field to Standard Value Set
Some of the standard picklist fields in Salesforce have their values defined in Standard Value Sets. This means when you add a new value in the Salesforce UI, for example in the Type field of the Case object, that you are actually editing the CaseType Standard Value Set and not the Case Custom Object.
Gearset detects all these differences, but it isn't obvious why Case.Type appears as unchanged in a Gearset comparison. It would be better if Gearset showed some help text in the Case.Type object definition that pointed me to some help docs or linked me to the exact…
2 votes -
Show Workflow Activities As Dependency of Parent Workflow
When selecting a Workflow Rule, its dependent components (i.e., email alerts) are not shown in the dependency view. They should be.
2 votes -
Support for zipping and unzipping static resources in GIT repos.
Add support to automatically unzip zipped static resources when migrating to a GIT repo and re-zipping when migrating to SF. This would allow me to edit my static resource files without having to manually unzip them.
2 votes -
AWS CodeCommit ability to view Repos
Today the ability is not there to allow for viewing multiple repositories within AWS Code Commit. One can view a singular repo and the branches that it contains.
In our instance we have different repos for our various instances. We would like to be able to have the ability to go on level deeper and be able to first choose the repo, then choose the branch.
Hit me up with any questions please.
2 votes -
Create a VSTS Build Task for Gearset
VSTS offers the ability to create build definitions to validate/deploy your code, but Gearset customers don't have much options natively in VSTS to trigger a Gearset deployment. We can scan a code repository for changes every 4 hours in order to do a CI deployment-- but that's about it.
VSTS offers the ability for vendors to create "Build Tasks" for their applications, where you can initiate a VSTS build and get results. This is basically a controlled version of API access to the tool.
More information:
VSTS Marketplace - https://marketplace.visualstudio.com/vsts
VSTS "Add a Build Task" - https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-build-taskIt would be…
2 votes -
Provide a way to deploy push topics
We have a push topic that we use but there is currently no easy way to deploy changes between orgs. Would it be possible to do this via Gearset?
2 votes -
Have the option to attach test details to test notification email
When you set up notification options for test monitoring, there should be a checkbox for attaching the detailed test result csv file to the email
2 votes -
Warn if a selected metadata type is not supported by selected API version
In the custom filters dialog, if you select a metadata type that is not supported by the API version, the compare and deploy currently just silently ignores that item, giving the impression that the compare has failed. e.g. selecting "Duplicate rule" with metadata version prior to 38.0.
It would be good for Gearset to provide a warning if a selected metadata type is not supported by the selected API version.
2 votes -
I need TeamCity to kick off a deployment within GearSet when all my auditing constraints are met.
We currently have a deployment pipeline for our .net and Rails environments that utilize VersionOne, GitHub, TeamCity and Ansible to deploy changes into AWS.
Due to auditing constraints we would like to use VesrionOne, GitHub and TeamCity to deploy our SF changes.
Does Gearset interact with these tools or must it stand on it's own?2 votes -
Show status in Chrome tab title
In Chrome, it is possible to display info even when viewing a different tab.
For example, I see this done with financial sites when they want to show the value of a stock ticker symbol.
2 votes
- Don't see your idea?