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.
369 results found
-
Cloning package should copy over (prepopulate) description as well as friendly name.
I find myself having to go to the original deployed package to copy the description information or coming up with a new description for the cloned package. Would be nice to have this brought over from the original when cloning a package.
17 votes -
Preserve spacing in formulas!
When deploying components like workflow rules, workflow field updates, and validation rules, it would be great if the spacing (i.e. carriage returns) did not get lost after deployment. This is especially frustrating for complex formulas where care has been taken to properly indent the formula for easy maintenance.
6 votes -
Allow other Enterprise Users who do not own the CI Job to run it
Enterprise Users can only "Run Now" Jobs that they own. If the Source and Destination Org are shared, allow other enterprise users to run the job.
46 votes -
Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed
Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed. Moreover after all object are select with filters for movement, please show the total number of records that will be migrated across all selection and its related objects. This will tell us if we are exceeding the limit of 10000 and do we need to split.
2 votesHi,
When you select objects for a data deployment, you’ll now see how many records the source contains for that object. This will also take into account any filters you have on the object.
We’d love to hear if this is useful or if there’s more you need – please get in touch via the in-app chat!
Tom
-
Allow Migration of Data Records to Production
Salesforce CPQ uses Data for things that are traditionally done with meta-data. Due to this pricing logic, production configuration information, approval logic, and pretty much the entirety of the package is controlled with data.
Gearset has limited its data migration tool from being able to deploy data to a production org. This renders it useless when working with Salesforce CPQ and has me recommending competitors over Gearset to clients. Gearset is a better UI & workflow than other competitors, but this is a major flaw that should be removed!
3 votes -
CI job edit - unable to change value of checkbox Filter By package.xml
everything else is editable; this checkbox is not
1 vote -
Upload Manifest File When Creating Scratch Org
When spinning up a SalesforceDX scratch org, allow a manifest file to be included. One use case is for when the Dev Hub org has PersonAccounts enabled and that feature can be enables upon creation of the scratch org.
2 votes -
Add support for the CspTrustedSite metadata type
It would be nice if Gearset could add support for the CspTrustedSite metadata type (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_csptrustedsite.htm) to its supported metadata list.
1 vote -
Add support for the PlatformCachePartition metadata type
The Salesforce metadata Api supports the PlatformCachePartition metadata type (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_platformcachepartition.htm), but it's not currently available for comparison and deployment in Gearset.
Can you add it to the supported metadata types list in Gearset?
2 votes -
Add a "Clone Package" to the Validate packages tab
Allow users to clone a validated package just like that can clone a deployed package.
3 votesWe’ve now added a dedicated Clone Package action to the validated packages table for Enterprise users.
-
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 -
Add the Deployment Friendly name to the Deployment Report
On the deployment report pdf can we add the deployment friendly name above the deployment notes.
3 votesThis has been completed and friendly names will now appear on the deployment report.
As always, feedback welcome!
-
Commit-by-commit deployment
As you are giving an option to trigger the CI job based on repository commit, it would make more sense to only compare the source and target based on the commit items and consider the commit changes for deployment based on your selection of either new, modified or deleted and the comparison filter(which can be optional in this case).
This will help in reducing the chances of overriding the changes of other teams working in a shared environment or an environment not in sync with the branch.
There can be other scenarios where we maintain managed package items in the…
43 votesThis was released on the 23/03/2021. Documentation is on https://docs.gearset.com/en/articles/5069914-delta-ci
-
add the ability to deactivate an invitation.
Hi, I think the system needs the ability to deactivate an invitation. I sent the invite to the wrong email and I don't see any way to deactivate the invite. other than copying the link and signing up with my account. I realize it expires after 3-5 days but i sent it joe123@gmail when I should have sent it to joe124@gmail and i just don't want to risk an unknown user getting into our metadata.
2 votes -
Allow us to configure a push notification when comparisons are done.
It would be great if we could configure a notification when a comparison completes. Sometimes comparisons take a long time!
7 votes -
When creating a scratch org, allow a user to define the expiration number of days
Currently, when creating scratch orgs, the system automatically sets the expiration to seven days. However, scratch orgs can last as long as 30 days. Would it be possible to define the expiration number of days during creation?
2 votes -
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
- Don't see your idea?