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.
1140 results found
-
Improve audit API to extract list of users and their entitlements. Additionally, allowing us to provision & deprovision user access via API
We use 3rd party tools to audit all of our user access at our company. Automating this via API instead of exporting CSV and loading that into another tool would be very beneficial. Additionally, we use that tool for provisioning and deprovisioning so if an API for that existed too, we could automate Gearset users.
3 votes -
Schedule Release Validation
We've run into ROW LOCK issues in the past while running unit tests during validations in production which caused some issues with external Community Users, thus as a best-practice we try to run production validations after business hours.
I'd like to be able to schedule release validations from Gearset, or expose an endpoint that would allow me to trigger a CI validation for a release or PR.
1 vote -
Add a date filtering mechanism on comparisons
. Currently we can select individual dates on the dropdown list or select from a select few "Last X days". Would be a great option to be able to set something like "See changes from X to Y" or "Select since X", especially useful given we have the dropdown selection on a per minute step, so the list gets very large, very quikcly.
For compliance checking, tracking who changes what when, periods of criticality (especially around new features coming in) or just for retrospectives.
1 vote -
Ignore line endings in pipelines conflict resolution
It would be useful if the pipelines conflict resolution tool ignored line endings. As at present if you have one file with LF line endings and another with CRLF it will show the whole file as different, where as that is not the case, it's just line endings. Most other devOps tools work in this way.
There is another idea to ignore whitespace in apex comparisons - but this should also be extended to conflict resolution.
1 vote -
Change Order of Steps for Data Deploys
When configuring a data deployment, currently "Planning Deployment Steps" is the last step, but this is where I often encounter the "Error while planning deployment" because of recursion/etc. That means I need to back up through the previous 4 steps, adjust, and then go BACK through the related objects, data masking, disable rules steps before it will try again.
The disable rules step in particular takes some time, making this a really tedious cycle to repeat.
I understand needing the related objects step before validating the deployment, but if the order changed to:
- Select Objects,
- Select Related Objects
- Plan Deployment…
1 vote -
Please introduce an external ID in the background as some other products do. This would make it flawless.
Without the external ID, your solution is time consuming and prone to troubleshooting errors.
1 vote -
Deployment pipeline view personalization
Currently, the view in continuous integration (deployment pipeline) is sorted by ABC, which is not user friendly when there are many team members. In this case I appear last and I need to find myself in this screen.
I suggest you to either:
1. allow creating personal views per user, so I can see only my dev sandbox, full sandbox and production.
2. change the scroll into a "regular" scroll, and not the current drag scroll4 votes -
Gearset Unit Test Monitoring ignores test methods in classes at V27 or earlier
For older orgs, one may have Apex classes at V27 or earlier. Such classes were allowed to also include testmethods.
Gearset's Monitoring job ignores these test methods leading to a false sense of security that one's org is "correct"
Example class is at V24
class Foo {
void doStuff() {}
static void testmethod myTest() {
new Foo().doStuff();
System.assert(...);
}The myTest will not be run by Gearset Unit Test Monitoring. It will be run by Setup > Apex Test Execution > Foo > Run tests
2 votes -
Permission set changes not displaying without drilling down
You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI
2 votes -
Help users Deploy Sales Cadences between orgs
Sales Engagement for Salesforce allows users to build Sales Cadences. These seem to be record based, so being able to move these between orgs would be great.
1 vote -
Enable data fixes when migrating Vlocity datapacks
When the data in the source and target environments are aligned, deploying Vlocity datapacks with Gearset can be quite straightforward.
However at times when they are not, deployments can fail catastrophically with the documented solution requiring the use of tools provided by Vlocity / Salesforce Industries in their Vlocity Build Tool : https://github.com/vlocityinc/vlocity_build. The alternative is to try manually resolving the issues, which can be an uphill struggle when you consider complexities around products, such as their hierarchy, availability and pricing.
For Gearset to truly be a one-stop tool for Salesforce Industries deployments, please enable data fix functionalities in…
1 vote -
Add Manage Custom Filters option when creating a CI job
When I use options Automation -> Continuous Integration -> Dev Sandbox -> Compare and commit for deployment, there is no option to create a custom filter.
Custom filters can only be created by using Metadata deployments -> Compare and deploy option.
Since the following tutorial https://docs.gearset.com/en/articles/6166062-promoting-your-first-features recommends to use Automation -> Continuous Integration for deployment, it would be nice if this way of deployment also had an option to create custom filter.1 vote -
Share org connections or CI jobs with sub-teams
As an SI, we use Gearset for release management with multiple clients. Each client has multiple environments and CI jobs, but not everyone on my team works with every client. Currently, I can either share an org connection or CI job with all members of my team (providing access to people who should not have it) or I can share it individually with each person working with the client (which can sometimes be up to 10 people). It would be useful to define a group that holds the people who work on the client account and then share org connections…
1 vote -
Remove files from a PR
I want the ability in Gearset to selectively remove files from a branch or PR without running another comparison.
I have an admin that frequently "over commits" too many things.
Often its bad enough that its just easiest for them to delete the branch in github then start over in gearset.
The problem then is that starting over from scratch, a day or two since they worked on it, and they will make a different mistake.
I'm aware of a few features, like
Delete the branch in Github and start over in gearset
- Seems to be the easiest to me
…
8 votes -
Environment variables - Clone
Hello Team,
We would like to have the possibility to clone already existing Environment Variables when setting up a new Environment.
This functionality will allow us to refresh and create new environments faster and prevent us from performing specific commits in branches and specific configs per new environment.
3 votes -
Monitoring dashboard page hangs on loading
Often, if not always, when I first load up the monitoring dashboard it hangs on the loading wheel until I refresh. Doesn't appear to be a problem on any other page.
1 vote -
Delete feature branches in Github in a way that they can be restored
I closed a PR to master, and Gearset deleted the feature branch. However, it wasn't merged, so I wanted to restore it to continue work. I was completely gone from Github. I believe Gearset should do a normal delete that allows restoration instead of completely obliterating feature branches or allow an option to do so.
4 votes -
Get Notified if Pull Requests or Validation Fails
Our Org has Gearset Officers who handle promotions. It happens at times that I create a pull request and have it start validating (which can take a while). I'll navigate away from the screen and totally forget about it, assuming it'll get pushed to the next environment.
But sometimes there are merge conflicts, or validation fails. I'd love to get a notification, either in email, or as an integration to an attached jira ticket that it failed. That way ill be notified by slack or whatever.
Just an addendum here. We use 3 environments. Admin, UAT, and finally Production. When…
5 votes -
Add wildcard Test selection
When selecting tests to be run for validation or CI validation jobs, we should be able to select "Test classes" and provide more generic search names such as "Test.cls" or "classes/". This would allow dynamic updates to the selected tests based on available test in the deployment package.
1 vote -
default repository
Allow to set a default repository when you have multiple repositories.
- Navigate to Compate and Deploy
- Select Source Control and select a VCS(in our case Gitlab Self Managed)
- If you have dozens of repositories they all show up on the list
- Need ability to specific a default repo which will be auto selected
2 votes
- Don't see your idea?