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.
1380 results found
-
Store formatted JSON in source control
The SFDC metadata API returns some items types as JSON compressed to a single line. For example, this applies to Wave dashboards (.wdash files).
Gearset neatly expands this to a more readable when visualizing and comparing.
However, in source control Gearset stores them in their original one-line compressed format. As a result, when doing merging and conflict resolution at the source control layer, these items are impossible to handle, as any change (whether technically conflicting or not) results in a conflict from git's point of view.
It would therefore be great if Gearset kept the expanded format for JSON data…
2 votes -
Give Permissions to Edit Automated Job Settings
Adding a feature to give users permissions to edit & delete Automated Test Jobs would be great. Today I had to hunt down a colleague to be have him edit his job when all I had to do was change the schedule. This feature would have saved a lot of time.
2 votes -
Add the option to purge on delete
The metadata API has a boolean option to "purge on delete", i.e. permanently erase deleted items rather than just moving them to the recycle bin. This option is not exposed in Gearset currently, but rather hardcoded to "false". For CI scenarios in particular, it would be extremely helpful to be able to specify that this option should be set to "true" for deployments.
2 votes -
Be able to start immediately a JOB (CI/Unit Tests/Monitoring)
Add a button to start it immediately. Currently only solution is to change the executing time!
2 votes -
Allow bulk org access for new users, new org permissions upon adding
When adding a new user having the ability to give the same level of access to all orgs at once would be greatly beneficial.
Likewise, when adding a new org and having the ability to set user access to the new org would save time as well.
We are adding new orgs frequently and will be adding users as well. Saving time on permissions would be great!
2 votes -
test Monitoring overview - show "is running" + stats
On the Test Monitoring Overview page; you should be able to see at a glance whether the test is running and how many methods have run vs total
Reason this comes up is if you establish a Unit Test run for your developer sandbox org, then you can't run (some) tests from your IDE against the same org "ALREADYINPROCESS Test already enqueued"
A quick glance at the Test Monitoring Overview would tell you if you need to wait 1 minute vs 20 - and guide your activities accordingly
2 votes -
Support parallel testing during CI job
CI jobs use metadata API to deploy and run tests. The tests run serially. As such, CI jobs can take many minutes to execute
As an optional configuration for a CI job, and only if the CI is run against a non-PROD org...
- Deploy metadata using Metadata API
- Run tests using Tooling API (parallel testing)
- If tests fail, use MetaData API to rollback the deployment
Ideally, this can shave off 50% of the CI job time
2 votes -
2 votes
-
Suppress "changed on" datetimes in difference viewer where datetime is the same as the metadata retrieval datetime
The difference viewer will show Changed on values for the current datetime for certain metadata types - probably because SFDC is returning such a value when, in fact, the source didn't change at all
- Custom object
- Settings
- Standard valueset
- Workflow rules
displaying the current datetime of the compare run (i.e. the metadata retrieve datetime) is not helpful when trying to filter on changed date in the difference viewer (i.e. sort descending)
2 votes -
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
- Don't see your idea?