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
-
Invoke Run Anonymous Apex against target in CI Job
Team,
Can you please add Run Anonymous Apex option in a CI Job ?Step#1
In this scenario from Developer's end they should add pre scripts in a.txt file and add post scripts in b.txt file in their Source ControlStep#2
How it should work
- It should allow the CI job to run Pre and Post Deployment scripts
- Pre Deployment scripts should be picked up from Source control a.txt file and Post
Deployment scripts should be picked up from Source control b.txt file
- Post commit the diff of commit should identify what are pre and post scripts…6 votes -
automatic pipeline deployment on successful validation
For Pipeline jobs, provide an optional feature (ability to toggle on/off) where if an Open PR has successfully validated on the target org, then auto deploy to target org. This is useful when propagating changes in downstream jobs. For example, once code review is done, a PR is merged into DEV by pipeline admin, but it should also automatically be merged and deployed into QA if the validation is successful.
5 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 -
Update Deployment Functionality for Education Cloud Standard Picklist
Currently, Education Cloud standard picklist field values are able to be deployed to production. However, the deployment lacks the ability to define active or inactive picklist values. The workaround is to manually activate and deactivate these values after deployment.
This functionality was recently changed on 8/17/2023 for the Academic Session Season and Academic Session Type fields. Requesting the change to be made for all of these fields. Salesforce Education Cloud developer docs (https://developer.salesforce.com/docs/atlas.en-us.edu_cloud_dev_guide.meta/edu_cloud_dev_guide/edu_cloud_intro.htm)
2 votes -
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 -
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 -
Allow users to select custom fields even if the object does not exist in the target
Would be great if GS allowed to select custom fields when doing a comparison even if the object does not exist in the target. If I am pushing changes to a repository I might want to only include the fields I created/modified and not the whole object.
15 votes -
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 -
Attach specific Tests to Feature Branch Manually
I would like to have the ability to force a features jobs to run specific test(s) from the CI screen.
So if GS fails to detect a test class (either by error or b/c its not named in the expected convention) OR would have failed to catch breaking changes elsewhere, we can avoid/prevent this attaching a set of test classes to that feature branches deployment configuration in GS.
2 votes -
Add the package Name to the page, when the package is Opened
Currently when you Open a package like a draft deployment, the Name of the package does not appear. There is a message in top L-H 'Comparison finished' which is not very useful. Perhaps the package Name could go here. It will reduce confusion as you will be able to tell which package you have open. Thanks.
2 votes -
Disable Pipeline Back-propagation for Static Environments
We would like to have the option to disable the back-propagation in the pipelines for static environments or have more options to control how the back-propagation should behave, like not running the PR validations for these types of Pull Requests.
When new changes reach the master branch, those changes should be pushed to the branch linked to a Salesforce environment. As it is today, the changes are back-propagated through new Pull Requests and because of the pipeline default config, the unit tests need to run which can block the sandboxes for some time depending on the complexity of the release…
3 votes -
Ability to report on runtime in Gearset Reporting API and what metadata filters were used
As part of showing the amount of time saved by using Gearset (and DevOps best practices), as well as the overall current utilization of Gearset across multiple teams and Gearset instances, being able to report on the Comparison, Validation, and Deployment runtime would be extremely beneficial. Also reporting on which metadata filter was used, if named and saved/accessible, in a comparison, validation, and deployment.
This data could also be used to identify inefficiencies in the standard metadata filters used across our Gearset instances, and potentially identify clients not deploying smaller and iteratively in order to prove with data how that…
5 votes -
CI job merger conflicts
When resolving CI job merge conflicts, a user has two windows to accept changes from one side of the window. Can we have an option to accept specific components changes from one side and certain changes from the other side.
4 votes -
Pipeline Sync Environment & Dev Environment
Currently we only have the ability to sync static pipeline environments. This is well and good but unfortunately syncing the Project branch can be time consuming and confusing Its not as simple as syncing the static environment.
I suggest when I sync the static environment , the sync action automatically opens a back propagation PR to the Dev environment its connected to. Also this sync action should close any pending open PRs against that dev environment that overlap with the sync PR.
2 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
- Don't see your idea?