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.
337 results found
-
Add the ability to filter by Date to Data Deployment
It would be very helpful to some processes I run if I could do data deployment filtered based on date - date created specifically. I am trying to migrate some test data from Production to QA/User Testing and I get duplicates now. A filter on created date would solve the problem entirely.
1 vote -
Ability to change the value of a field on import
Price Rules have Price Conditions and Price Actions and sometimes Lookup Queries hanging off of them as related objects. Some of the price rules wouldn't get created because there is a field called Conditions Met and it equaled Custom. If we were doing this migration via data loader, I would set those records to equal All for the value just to get the price rules in. Then we would load the Price Conditions. Then we would do an update to the price rules to set it to what it should be - Custom. We cannot save the record initially with…
1 voteYou can now deploy Price Rules and Price Conditions when Conditions Met is set to Custom. You’ll need to have either All or Any set as the default picklist value for the deployment to work.
It’s also possible to deploy Product Rules and Error Conditions, and Approval Rules and Approval Conditions.
-
Allow default repo to be set in Manage Connections and use in Comparison
This does not appear to work.
- Setup connection to source control GitHub that your user credentials includes multiple repos (in my use case, there are about 100)
- Do a Comparison, in the target list of repos, you will see all 100
- Select your repo (say repo #77). Do the Comparison
- Logout
- Login. Repeat step 2.
RESULT: repo#77 is not defaulted. You have to reselect it.
Either fix the aforementioned issue so the repo you most recently used is 'sticky' or allow specification of a default repo on the Connections page for each repository type.
1 vote -
Fix Keyboard shortcuts for selecting differences
When I have a lot of changes to review I'd like to use arrow keys to go up/down and expect "space" to toggle the checkbox for that. However the checkbox focus doesn't move with the highlighted row - so it doesn't work :(
1 voteThis has been completed and Gearset now has the shortcut keys you’d expect.
Thanks,
Kevin -
Sort order of Orgs ignores friendly name
If you have friendly names for your org connections, the list of orgs presented on the Comparison page ignores these and instead sorts on sandbox name. Since the lines show friendly name left most; this is not natural to the human to see things out of order
Example
OrderFix (joe.blow@foo.com.story003)
Invoicing (joe.blow@foo.com.story010)
AlphaTest (joe.blow@foo.com.story091)when what the eye wants to see is:
AlphaTest (joe.blow@foo.com.story091)
Invoicing (joe.blow@foo.com.story010)
OrderFix (joe.blow@foo.com.story003)1 vote -
After choosing source/target connection: show friendly name.
When we are selecting source/target we can see the friendly name in the dropdown list.
After the selection is made we can see only the username. It would be easier visually confirm that correct connections are are selected if the friendly name was shown next to the username.
1 voteThis is now completed, and friendly names will appear in the dropdown where you select the org
-
Active Link to Deployment Destination
When you finish a deployment you get a "Deployment Summary" screen that has handy details. It does not, however, have a link to the commit/branch in Github or other site where the destination ended up. I have to jump to my Github page and refresh instead of having a direct link. Yes, it's a tiny feature but is useful for a Gearset newbie like me.
1 vote -
Clickable Jira Request within Deployment Report
I would like the ability within the deployment report to make the jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
1 voteThe Gearset has made this feature available for Jira tickets and Azure DevOps work items, thank you for your suggestion.
-
Show a browser alert after a long running operation
Some operations, such as a comparison or deployment, can take some time. I normally navigate to another tab. It would be good to get a browser alert when the operation is finished and I'm needed again
1 voteThis has now been completed
-
Remind me what I just validated
I am working on 10 things at the same time like usual. I started a validation about an hour ago. I open the tab where the validation was occurring and it says it succeeded. Yippie! Problem is I don't remember what I was validating and nothing on the success screen tells me which system I was validating against. I want to be sure I am going to deploy the right thing to the right server at the right time.
Can you add the name of the destination system (at least) on the success screen so I can remember what I…
1 voteThis information is now displayed on successful validation.
-
Include select all option for Manage Custom Filters
Selecting individual items to include for custom filters is a laborious process. We have to exclude 6000 items and we are unable to do this manually. Please add the select all option when using a filter in the manage custom filters dialog so multiple items can be selected at once.
1 voteGearset now has a `Select all` option for named items on custom filters.
Thanks for your feeback!
Thanks,
Kevin
CEO, Gearset -
Display API version underneath source and target on Comparison In Progress and other pages
When deploying from org to GIT or vice-versa, the API version being used should be echoed (small font) everywhere the source and target names are shown (such as at top of Comparison in Progress)
This is especially important for GIT where Gearset in the absence of other info will default to V37 that in turn causes issues with picklist comparisons. It can also be important during Sandbox Preview of new releases
1 voteWe’ve now shown this on the `In Progress` page.
If there are other places you’d like to see it, then feedback always welcome to submit an idea for that specific page!
Kevin
-
Static code analysis - allow for exclude patterns on classes
The new static code analysis feature using PMD is a good first start but there are too many false positives to make this useful
Here is one place to start:
Allow for specification of regex patterns to exclude classes. Specifically, classes that start with xxxx_ would be most helpful as it would allow us to remove from analysis unmanaged packed code like fflib (Enterprise Patterns) or sfab (SobjectFabricator). There are hundreds of lines of PMD rule alerts from these classes
1 voteTeam owners can specify exclude patterns on the rule set configuration page.
-
Export Comparison details all items
In the comparison details the tab "all items" it should have the ability to export the table
1 vote -
bug -- Refresh comparison with a selected item that on the refresh is no longer changed
If you have a piece of metadata that was changed on a comparison then a subsequent comparison using the 'Refresh Comparison' button. The selected item is still selected and unable to be deselected.
1 vote -
Trialforce ORG Type Support
Hey Gearset!
I want to do some testing with the Data Deployment beta feature, and i realized something. Most of my testing is done on Trialforce ORG's (Trial ORG's that are generally identified as a production type ORG). Is there a way that we can delineate between true production ORG's and a Trial ORG and have the Trial ORG as an option to deploy data to? Current options are Sandbox, Developer, and Production.
Thanks!
Richard Scott - AHM
1 vote -
Refresh comparison
In the Deployments > Comparison History view, there is currently the action to "View Comparison" but it would also be nice to have a "Refresh Comparison" button next to it.
1 vote -
Support Wave Analytics Metadata
We have been engaging in quite a few Salesforce Analytics (ie. Wave Analytics, Einstein Analytics or whatever the current branding label) projects lately. Version control on all of the related metadata is critical it would be enormously beneficial for Gearset to be able to support these metadata elements.
The following Analytics metadata types are supported in the Metadata API:
WaveApplication
WaveDashboard
WaveDataflow
WaveDataset
WaveLens
WaveXmd
WaveTemplateBundlePlease consider adding this to the roadmap for immediate consideration!
Best regards,
Mike1 voteThis has been shipped and we’ve written up an overview of the feature: https://gearset.com/blog/gearset-and-einstein-analytics-deploy-wave-applications-with-ease
-
Add webhooks for VSTS (like BitBucket and GitHub)
You offer webhooks for BitBucket and GitHub source control branches (so you can build on-demand if the repository is updated). We use VSTS Git at our organization and this functionality would be really useful for us!
VSTS offers webhook functionality-- see here: https://www.visualstudio.com/en-us/docs/marketplace/integrate/service-hooks/services/webhooks
Please give it a chance!
1 vote -
Add button to go from validation package to comparison
Use-case is where we have validated a package, but not been able to deploy it before expiry. Eventually, we are able to deploy it...
At this point, I'd like to be able to go from my validation package in the history straight to a comparison with the same objects selected. Then, I'll be able to make sure everything still looks good and validate/deploy again.
1 vote
- Don't see your idea?