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.
1152 results found
-
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 -
Indicate from Gearset if a deployment is eligible to use Quick Deploy
I would like to be able to see from Gearset if a deployment is able to utilize Quick Deploy. This would be particularly useful for releases to production as we release after hours and our unit tests can take many hours to run. Knowing that Gearset will use Quick Deploy will increase our confidence with our release and reduce mental load knowing that the deployment will be much more likely to succeed.
1 vote -
Gearset VS Code Extension
My development team spend their time in VS Code where they can see all their Git information etc. It would be great to have a Gearset plugin to stop them having to switch windows and allow them to have information at their fingertips. This could also encourage more developer use of Gearset.
May display:
- Build status
- Static code analysis issues
- View of pipeline1 vote -
Remove limitation of number of PRs to be added to a Release (Azure DevOps + Gearset)
Gearset automatically adds all PR details for a release in description box (Azure DevOps PR) which has max character limit of 4000 and only 16-18 PRs can be added to a release because of it. When we add one more PR after the limit is reached then the next PR does not get added to the Release and we need to create another release for them which is not correct approach as other releases may have some dependency on 1st and thing may fail in production. We need a way to disable adding description to Azure DevOps Release PR so…
2 votes -
Download Package Option does not include custom fields.
Just wanted to flag that the Download package option would be so much handier if it also included custom fields. Even with custom fields selected in my comparison, the package.xml that I can export only includes the Objects.
1 vote -
Enable us to customize the Slack notifications from Gearset
Enable us to customize the Slack notifications from Gearset (e.g. add deployment Friendly name to Slack deployment notifications). Thanks
4 votes -
Allow multiple connections to the same source control system
Currently you can setup as many salesforce orgs as you would like as a source/target but you do not allow the same with VCS/Source control systems.
For example, I can only tie a single account to a single bit bucket. What if you have muiltiple bitbucket accounts that have different accesses to different repos - there is now way to do this in gearset.
You should expand the source control systems to be just like the salesforce orgs - you can configure and share as many as you would like for the same or different systems.
1 vote -
1 vote
-
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 -
Add "View Validation in Salesforce" to your Github and Teams/Slack Channel messages.
Our pipeline is utilized by some implementation partners that we do not give access to Gearset. They manage their changes that flow through the pipeline with GitHub and receive pipeline updates in a Teams channel. Both of these options have a message to view validation errors in Gearset but the partner teams cannot see Gearset. If these messages included the same "View Validation in Salesforce" option that lives in Gearset, they could be redirected to the Salesforce error page to help their troubleshooting faster.
10 votes -
allow configuration of problem analysers for different target locations
If we could turn of problem analysers for specific locations (e.g. Git repos) this would allow us to remove irrelevant problem solutions from our git commits, but keep them for deployments
1 vote -
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 -
distinguish between components of feature branch and what is syncing to main
As a user of gearset deploying pull requests to multiple environments
I want to be able to identify actual components of the feature branch vs. what is included for syncing to main/main branch for the org being deployed to
So that there isn't the confusion of understanding what new/changes items are showing up in the commit information1 vote -
Ability to automate deployment to a particular environment without manually promoting changes
When there are multiple Salesforce environments in the deployment pipeline, like Integration, Qa, Stage and Production, we would like to have ability to automate deployments to a specific environment, without having to select PR and promote changes manually. Most of the times SIT/Integration environment will be used for Developers to be able to perform integration testing, where we do not want someone like a Lead to review and promote PR manually. It will be beneficial to deploy the changes automatically, as soon as someone creates the PR to the Integration environment.
9 votes -
Create a link in the main menu under Data Deployments for managing Data Deployment Templates. It is not very intuitive to manage them curren
Create a link in the main menu under Data Deployments for managing Data Deployment Templates. Having to start a deployment in order to manage the templates is not very intuitive.
1 vote -
Automatically Defer Sharing Calculations
Salesforce has a feature to "Defer Sharing Calculations" ( https://help.salesforce.com/s/articleView?id=sf.security_sharing_defer_sharing_calculations.htm&type=5 )
It would be awesome if Gearset Pipelines could have an option to utilize this, if sharing rules are included in Deployment, defer sharing rules for any validation / deployment, re-enable and recalculate after deployment
1 vote -
Please add Namespace/Package name as a column in the comparison view
Currently , if I pull down metadata from managed packages (e.g. with the intention of committing the custom fields we've added to managed objects or committing the permissions we've updated) this means I get all the metadata in the comparison screen, with no way of filtering out the managed packages. An example of where this is a problem/cluttering the UI is Triggers/Classes - the contents of these is always hidden, so ideally i'd like to have a column to filter them out
1 vote -
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 -
Ability to rerun deployments
We had a deployment in a pipeline that included a change in a managed package. the MR to the environment branch has the permission set change (access to a managed package field), but the Pipeline did not deploy it. It would be great if there was a way to "re-run" an already promoted branch, as we can't use a MR at this point to trigger, since the repository already has the change.
1 vote -
Provide deployment history by Salesforce ID or My Domain
If we could have a way to quickly export all changes to specific environments regardless of user who created the connection, would be ideal.
Use case: Provide a Production OrgID and be able to export all changes across all connections and manual compare-and-deploy and pipeline deployments.
1 vote
- Don't see your idea?