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.
1469 results found
-
See Continuous Integration Deployments in the Deployment History tab
List deployments resulting from a CI job on the Deployment History tab along with manual deployments.
We currently deploy metadata using both manual and CI jobs and it would be convenient to see all deployments in the same list (for debugging, reporting, monitoring).
5 votes -
Add default compare filter - Code changed by me today, changed by me last 7
A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days
Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes
Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order
This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…
5 votes -
Possibility to deploy to another sandboxe when a ci job passed
When configuring a CI job, we need an option to set a deployment to another sandboxe when the deployment or test classes run successfully in the current CI Job.
Ex: when a push to a branch on VCS triggers a CI job to deploy to a sandboxe like QA (with test classes run), we also have the possibility to set an auto deployment to staging sanboxe when the the job on QA passed successfully.5 votes -
FLS selection for Source control
while deploying a field to source control. we just want to move profile FLS of that only field. FLS was not displayed on the components drop down of profile. we are only able select profile so that whole object's FLS are getting deployed to the Source Control.
5 votes -
Allow option to select certain test classes to NOT run. Include an exclusion list of tests not to run
When deploying code, it would be nice to have an option of having an exclusion list of test classes to not run.
5 votes -
Please, please, please get US FedRAMP approval.
The ability to use this product for CI/CD and various other use cases in the US federal space would be a huge win for many agencies. I know the FedRAMP process is quite arduous, but the contractual potential here is pretty massive.
5 votes -
Add deployment support for Macros
Macros deserve to be added to source control yet there is no way to do this with Gearset:
1) Data feature (paid add-on) doesn't deploy to/from source
2) PRO/Enterprise can't source/target deploy Macros because it is not available with the Metadata API.Since macros represent some debugged logic, managing in source control makes sense. Curiously, SFDC has chosen to make Documents available via Metadata API but not Macros
5 votes -
Trust Site
Right now, Gearset is down and we cannot use it. It would be good to have a trust.gearset.com site that shows what is going on and what the team does to fix the issue...
5 votes -
Allows admins to limit the available branches of a repository
When connecting a source code control system, quite often an integration user account is used that may also be used for other parts of the enterprise. Please allow admins to restrict the available repositories and branches so that users can only run comparisons for the branches they should actually have access to.
5 votes -
Access to Jira custom fields
we have a custom field we use that ties to a release number. It would be great if as an additional option to selecting tickets, access this field, set the value (in this case our release number) and have gearset pull all related requests in.
5 votes -
Enforce code coverage limits on CI jobs
Please set it so that we can force a code coverage check on deployments (including CI). I'd like to verify on the lowers before going through to production. Might be able to do this with test cases but should be able to on deployment.
5 votes -
Be able to switch the direction of a comparison/deployment
Sometimes we need to reconcile changes on an object between two orgs, where some of the changes have been made in Org1 and some in Org2. Having set up metadata filters, compared and deployed required changes from Org1 to Org2, it would be nice to be able click a button to switch direction to then deploy required changes from Org2 back to Org1, without having to go through the whole process of setting up a new comparison.
5 votes -
Include both dates on comparison export
The sheet exported from a comparison currently includes only one date column. It is unclear which org this refers to. It would be great if it included two columns (one per org) so that one didn't have to individually look up the item to determine which version is newer.
5 votes -
API to Manage CI Jobs
I would like an API to manage CI Jobs and Sandbox connections.
In our current workflow, we create new sandboxes and branches for large initiatives. Along with these, we need to connect the SB in Gearset, build the CI job, run it for the first time, and then tear it down when we're done.
We would like to be able to automate some of this.
- I have a branch and a sandbox
- I want to connect that sandbox in Gearset (would be great to do this programatically via api)
- create a CI job via api
- be able to run the…
4 votes -
Feature Request: Deployment Blocking Based on Daily Unit Test Job Status
Currently, Gearset lacks a feature to block deployment CI jobs to the respective environments when the associated daily unit test job fails. Implementing this feature would be advantageous in ensuring that appropriate testing quality gates are established to prevent changes from being deployed in the event of test failures. This enhancement would significantly improve our deployment integrity and testing processes.
4 votes -
Dependency-Aware Deployment Sequencing in Gearset
Currently, deployments in Gearset can fail when interdependent metadata components are deployed simultaneously without respecting their dependencies. For example, deploying a new Lightning page that references a report or dashboard will fail if both are included in the same deployment, as the referenced report or dashboard does not yet exist in the target org.
While the current workaround is to manually split deployments into separate feature branches based on dependencies, a more intuitive approach would be for Gearset to detect these dependencies automatically when multiple related components are included in a deployment. The tool could then offer options to handle…
4 votes -
Add "Open Branches" Tab to Development Sandbox Environments in Pipeline
The only way to deploy an existing feature branch into a development sandbox is to perform a manual compare and deploy. Previously, we had our developer sandboxes set up as static environments which allowed us to create PRs against them for "re-deploy". This is not possible with the new Development Sandbox format. I suggest another tab be added called "Open Branches" which will allow the developers to select a feature to pull and work on in their development environment. That way we get the benefit of easy compare & deploy instead of having to manually compare and deploy. This will…
4 votes -
precision deployment for Record types
precision deployment for Record types is required. currently when i try to deploy a record type gearset automatically adds all the picklist fields in that object. if we wanted to deploy only record type or only selected picklist fields currently its not possible. hence, precision deployment is needed for deploying record types
4 votes -
4 votes
-
Increase API call limits
There currently is a API limit of only 10 calls per hour for the reporting and audit API's. This makes it difficult when developing and testing applications that tie into the api. In our case we use the api to pipe the data into our observability platform for reporting and dashboarding. It would be nice to either increase to something not THAT low or to have a development override option of some sort that customers to request to temporary increase. I understand the need for some limits due to having a shared cloud platform but this seems to be on…
4 votes
- Don't see your idea?