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.
1244 results found
-
Difference Viewer custom object name: include suffix __c, __x, __mdt, __e, etc
When you look in the Difference Viewer, it is not clear at all by inspection which line of Metadata Type "Custom Object" is a standard object, custom object, platform event, custom metadata type, historcial trending object, etc.
For example, Custom object Foo__c displays simply in the Name column as Foo. This is a loss of information in the difference viewer, especially if one has similarly-named custom object metadata types such as:
Fooc
Foose
FooConfig__mdtthese display as
Foo
Foos
FooConfigThe full Sobject Name gives the user hints as to perhaps other related components that need to be…
3 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 -
Zapier Integration
An integration with Zapier will allow more customizations options for how we can integrate with other tools, such as Manuscript (fka FogBugz).
1 vote -
Please, please, please get US FedRAMP approval.
The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.
5 votes -
Extend Jira Cloud Integration to Releases and Bitbucket
We do the majority of our management via Jira and have it linked to Bitbucket and our test system so that we can manage everything via Jira. It would be great to extend the current integrations to more intelligently link the package to Jira tickets and the corresponding Bitbucket code and then push back to Jira the deployments in a more Jira friendly manner e.g. potentially creating/updating a Jira release for the deployment.
6 votes -
Optimize comparison list view
The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.
There is a common pattern for handling long lists like this, in…
3 votes -
Cache deployment inspection results
It would be great if deployment inspection results were cached, such that the results for an identical set of metadata are available without spending the time to recheck everything.
Use case: A comparison is performed and all changes selected. Deployment inspection is performed and recommendations are made for items to add/exclude. I select a subset of recommendations, and move forward with validation. The validation fails. The same comparison is reopened and again all metadata is selected (with the intention of selecting more of the add/export recommendations resulting from the inspection). At this point, the inspection is rerun, even though the…
1 vote -
Adjust dependancy on managed package versions for Apex[Class|Page]
We've found when developing classes against managed packages the class ...meta.xml includes the package version numbers. Problem is these are fixed to the exact version installed (e.g. 9.4, 9.3 etc. example below)
But then if the managed package is upgraded Salesforce, in its infinite wisdom, doesn't update these so when you come to deploy next time you have to go and manually update all the version numbers - or if you have a different version in another sandbox (to test the newer one) same thing.
Seems like something a cool deployment tool could handle and offer to fix up on…
3 votes -
integrate with Atlassian Stride for notifications
Gearset's ability to send notifications to Slack is great. I'd like a similar ability to send notifications to Atlassian's Slack alternative - Stride.
1 vote -
Add deployment support for Macros
Macros deserve to be added to source control yet there is no way to do this with Gearset:
1) Data feature (paid add-on) doesn't deploy to/from source
2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros
5 votes -
Trust Site
Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...
5 votes -
When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
4 votes -
Allow for custom metadata permissions to be included with a single click when custom fields are being deployed
For example; when adding new custom fields, you generally have to add the permissions as an additional line item to the deployment. Having a checkbox or something that will have gearset automatically add the permissions associated with the metadata currently in the deployment list would speed up the process. Users should also be allowed to deselect lines that were automatically added.
17 votes -
Build Comparison Manifest from pull request
It would be cool if the custom deployment configuration could be driven from a Pull Request . For example, in GitHub, the Pull Request knows which files were changed and approved. Why not use that list to instantly populate a comparison to create a deployable manifest to go from source control to org?
15 votes -
Ability to have automated process to maintain field list in Production environment
With GDPR, companies are required to provide justifications for all data that they collect. In Salesforce this means being able to identify why all fields in the system exists, categorize fields as PI, and provide business justifications. The ability to keep a list of current fields in a production instance of Salesforce that includes alerts when new items are added, or ability to sync that list out to another tool like Smartsheet, where other business users like a legal team would have visibility, would be incredibly useful.
1 vote -
Restrict source orgs
For example, deployments to a production environment should only come from the master branch of our git repository
4 votes -
3 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 -
Ability to add custom trigger points to trigger CI from source control
At the moment the tool allows you to only kick off CI jobs when a branch is updated.
This is actually limiting the capability of the tool in itself,
because services like Bitbucket allows you customize trigger points, as to when they should ping the webhook;
such as the creation of pull request, merging a pull request.The two trigger points mentioned above are specifically very important because you would want to run validation CI jobs on the creation of pull request or when the merge completes so that you can actually ascertain if your branch compiles.
Based on an…
11 votes -
Allows admins to limit the available branches of a repository
When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.
5 votes
- Don't see your idea?