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.
1394 results found
-
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 -
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.
3 votes -
Soft delete of deployment History
When a person deletes a deployment history that was successfully deployed, it would be good if that deletion was only a Soft Delete and could be recovered within 90days.
1 vote -
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.
5 votes -
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 -
Enforce Promotion Approval Rules
The current UI shows a green checkbox and allows you to attempt to promote changes between environments even if the merge request is unable to be approved. Looks like it in Gitlab there is an 'approved' attribute that may be able to be used.
Alternatively, can have some basic rules but would like it called out its not ready to Promote in the Gearset UI.
4 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 -
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.
3 votes -
Ability to export deployed components for specified period of time
Instead of viewing it by deployment package, it would greatly help us to be able to export all components deployed during a specific period of time. It would help to include the following:
Deployment friendly name
Source
Target
Date and Time
Deployment Status
Owner
Metadata Type
Name
Difference Type4 votes -
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 -
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 -
Precision Deployments (available for Layouts) for all the meta data
Precision Deployments for Layout is a great improvement, it would be great to have the same feature for other meta data, particularely for : Fields picklists, global value sets, List Views, Reports, Profiles, Permission Sets and why not Lightning Pages, now that the Dynamic Form is available for Acc, Contacts & Opp
24 votesAll - please let us known in the comments which metadata types you would like us to support next with precision deployments. Thanks
-
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 -
Allow download of XML files from the comparisons page
In some instances, we have to use the Metadata API to download XML files for analysis. However, the Metadata API is a pain to use. Even Salesforce recognizes this and suggests using a migration tool like Gearset to extract these: https://developer.salesforce.com/docs/atlas.en-us.246.0.api_meta.meta/api_meta/file_based.htm
Since Gearset retrieves these files during comparison, it would be great if there was an option to download them to a zip file directly.
Note: There is already a "Download Package" feature on the deployment page. However, we obviously can't add items to this page if there is no change between the orgs. So, if a similar feature were…
2 votes
- Don't see your idea?