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
-
GitLab for destination of comparaison
I can't compare my sandbox org as source against my git repo as destination of compare.
I can see : gitHub, bitBucket as destination but no Gitlab.
It would be nice I if I could choose Gitlab as well and update my repo from changes in my org.17 votesWith our latest release, you can now add connections to any git-based repository using a username/password connection. This means you can now use GitLab as the target of your comparisons and deployments. See how to set up these connections in this blog post: https://gearset.com/blog/deploy-metadata-to-any-git-repository
-
Correctly create Price Book Entries records with different currencies and updated PBEs when they are out of sync (or delete+insert)
1) Currently PBEs are incorrectly inserted with the company currency as apposed to the currency of the source record.
2) PBE's currency cannot be updated once created (SF restriction) but because PBE's should not be referenced by Id, (that would be a terrible design decision). It is quite possible to delete and recreate any out of sync records.
16 votesHi, this feature has now been implemented. You should now be able to deploy PricebookEntry records with multiple currencies when you select the “Create new records” deployment option
-
Allow multiple ownership in Gearset
Currently only the creator (owner) of Schedule Test, Monitor Orgs and Manage Orgs can edit these activities. It would be helpful if we could designate more than 1 Owner for these activities. Similar to granting access to the various orgs (Comparison, Validation& Deployment) it makes sense to also include an Owner access as well.
If this is not possible, having a transfer ownership button would be helpful for each activity.
Thanks!
16 votes -
Offer a hosted version of Gearset Deploy
As well as providing an installer, it would offer greater flexibility if you could also provide a hosted version of Gearset Deploy.
16 votesI’m happy to announce that we’ve now launched a hosted version of Gearset Deploy.
Simply visit the site (https://gearset.com) to try it out. If you have any feedback about the hosted version, please feel free to leave feedback or email the team directly at team@gearset.com
-
Enhance XML meta data comparison to ignore changes in XML order
In org monitoring we frequently get notification about changes an the only thing is a change to the order of the XML elements returned.
The XML is virtually the same but the order of elements returned changed from one day to the other.It makes differentiating "real" changes from those false positives time-consuming.
It would be great if those kind of changes could be ignored or if there was an option to configure the XML comparison behavior for each monitoring job.
15 votesWe’ve made this option available now. See https://docs.gearset.com/en/articles/2413367-why-is-xml-order-of-some-metadata-in-the-comparison-results-different for more information.
-
Remember last used Custom Filter, or set a Default Filter
It would be nice to be able to set a default custom filter.
Since the default "Default comparison" filter doesn't suffice for me.15 votesGearset will now remember the last used comparison filter.
-
More granular control over CI job schedules
Currently, a CI job that deploys from a Salesforce Org to another org or source control can only be scheduled to run at 4 hours intervals. Additionally, there is no mechanism of specifying when these jobs will run - instead, the job is scheduled randomly within the first 4 hours it was created and every 4 hours after that point.
Providing a smaller interval (ex. every 1hr) and/or more granular control over the job execution time seems like a common sense enhancement.
14 votesYou can now set the interval to every 1 or 2 hours. Can you see is this matches your request?
-
Ability for team members to manually run the CI
Currently, only the owner of the CI job can manually run the CI. If the owner is out or unavailable, this creates a problem for team members because they have to deactivate the current job, clone and setup the new CI OR transfer ownership. Transferring ownership doesn't work if a team member is out unexpectedly, ill or doesn't have access to perform the transfer.
It would be helpful if you could grant access to a group of team members who have access to manually run the CI. This would save a lot of time and prevent having to keep multiple…
14 votesWe have made changes to the app on the 29th of June release for Enterprise licensed Gearset users:
Added the ability to run CI jobs belonging to other users if the source is a git repo and the target has deployment access delegated.
We think this now covers the cases:
- Allow an enterprise licensed user to run other people’s org to org CI jobs
- Allow an enterprise licensed user to run other people’s git to org CI jobsWe have not implemented allowing user to run other people’s org to git CI jobs. As this is sub use case is quite a specific interpretation of the original suggestion. Perfectly happy for it to be specified in another separate suggestion.
We have updated the documentation to reflect this change – https://docs.gearset.com/en/articles/2533179-access-levels-in-gearset
I hope this delivers the what your team needs. Feedback always welcome :)
-
Allow Team Members to Run Scheduled Unit Test Jobs
Execute Others’ Unit Tests
John Doe creates daily unit test job for SuperHeros R Us. He schedules it to run nightly.
Jane Smith, a member of the same Gearset team, is responsible for doing the weekly deploy for SuperHeros R Us. The unit test job from the previous day has failed (it had been previously working). Jane makes updates to the tests, and needs to re-run the unit test job. But she does not have permissions and John is out on PTO for the day. So… she needs to do it manually.14 votesReleased on December 31st, 2020
Test monitors can now be run by anyone who has validation access to the org being tested. -
Include logic operator choices in Data Deployments
Currently Data Deployments only allow filtering on
[FIELD] = [VALUE]It would be beneficial to be able to include other logic operators such as:
NOT EQUALS
LIKE
IN
GREATER THAN
LESS THANetc.
14 votesWe’ve made lots of improvements to the data deployment filters over the past few months.
The filters now include:
- equals
- not equal
- greater than (or equal to) & less than (or equal to) for dates, datetimes and numbers
- is empty & is not empty for nillable fieldsYou can now specify multiple values (use OR logic) when using the equals filter.
We’ve made it easier to input dates and times so that you don’t have to rely on knowing the exact format.
There’s validation so that filters with invalid values aren’t possible. These invalid values would have caused the deployment to fail.
If there’s still further improvements that you need, please could you create (or vote on) a new idea? This will help us identify which improvements are most valuable to you.
Thanks,
Tom -
Ability to compare and migrate object data between Salesforce orgs
The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.
14 votesThis has now launched as part of our data deployment feature.
https://gearset.com/product/data-deploy
This is an opt-in feature, that doesn’t change the default security profile of Gearset for those users that choose to use metadata only
-
Deploy detected changes to other orgs
Being able to detect and roll back changes to orgs through the change monitoring is cool, but what I'd really like is to deploy detected changes to other orgs.
For example, if we detect a new configuration change to Production, being able to clone that change back down into our Sandboxes directly from the monitoring snapshot would be a real time saver. Or if someone deleted something in Production, being able to make that destructive change down into the Sandbox.
It would help us remove the step of running the comparison and pushing the changes after seeing a monitoring job…
14 votesThis is now shipped and live in the app! We’ve written a small blog post that walks through the feature and the use case.
https://gearset.com/blog/migrating-quick-fixes-in-salesforce-to-source-control
-
Identify that metadata is the same, even if ordered differently by metadata API
There are a lot of instances where the comparison will identify metadata as different, but the only difference is the way the API is ordering the XML. I've seen it happen a lot with picklist values on multi-select picklist fields. It would be nice to be able to turn this on/off somehow so that metadata that isn't truly different won't show up in the difference compare.
13 votesPlease see if anything else could be improved on in the feature description released in Nov 2021.
-
Add a Save As to Save Draft Deployment
Add a Save As or an alternative way to create multiple packages from the same comparison. I have an existing comparison run and I want to stage the deployments, deploying some today and the rest next week. It would be more efficient to save both packages now as I am going through them, saving one for example as Dep120916.1 with half of my selected object and another one called Dep120916.2 with the remaining objects to be deployed later.
13 votesFrom the results page, you can now select the Save as option from the button toggle menu.
-
Add an OAuth feature for connecting to your orgs
As well as the username/password option on the credentials page - add an OAuth option to enable connecting to the source and target orgs.
13 votes -
Add an option to disable the "repository sanitizer"
The "repository sanitizer" performs unsolicited/silently changes which confuse users and generate issues. For instance, if you have Apex class permissions in profiles for classes which are part of a managed package and are not present in the repository, this sanitizer will modify the permissions to false which is obviously a disaster, (and the changes can happen any moment, while users are trying to deploy something completely unrelated hence the confusion).
We know the solution is to have the classes also in the repository but for managed packages that's unnecessary extra work since then we need to be updating them every…
12 votes -
Improve Bitbucket Server integration for teams with large number of project/repositories
ideally... gearset should not be hitting https://adlm.nielsen.com/bitbucket/rest/api/1.0/repos
first. It should hit https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects to get a list of projects
then allow the end user to select the project
then https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects/{projectKey}/repos to get a list of repos on the project the end user selects12 votesGearset will now filter by project first when selecting a repo/branch for Bitbucket Server
-
Be able to create a CI Job to auto-commit (changes between two orgs) to source control
We have both admins and developers working within our SFDC environments.
Admins typically deploy across environments, so being able to create a CI job to keep the repo updated with these org-to-org changes would be ideal.
12 votesIt is now possible to choose a source control system as the target of a CI job.
For source control best practices, have a look at our whitepaper: https://gearset.com/blog/whitepaper-guide-to-implementing-version-control-for-salesforce
-
To make it possible to abort started CI job on Continuous integration dashboard.
At the moment, you need to wait until the comparison is finished and the deployment has been started and then you should go to the org to cancel running deployment. It would be useful to have an option to abort the CI job.
11 votesThis feature is now available with the latest release.
-
offer the capability to exclude items in a metadata filter using a regex pattern
If we can exclude certain things in the comparison filters, all other newly created things are automatically provided with the CI job that uses my comparison filters.
For example, at the moment in "custom filters", if I select the type "custom object" and disable "all elements", I can filter and choose which objects we want to compare.
-> We need the option to invert the filter. To be able to select the specific objects that do not want to compare and deploy (like "Not: regex: waste_ | QA_ | staging123_").
11 votes
- Don't see your idea?