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
-
checkbox
When viewing Open Pull Requests in an environment in a pipeline, the user can click the checkbox beside the pull request thinking they have selected that pull request. Clicking the checkbox does not currently select that Pull Request in the UI. It would be nice if clicking the checkbox would also select the current Pull Request in case another function such as "Close pull request" (trashcan icon on right pane) is being selected.
It is easy to think you have selected the pull request when clicking the checkbox for it and in turn close the wrong pull request as a…
1 vote -
Enable AccountContactRelation standard object as part of data deploy
After chatting with support, it seems to be impossible to deploy an AccountContactRelation record when IsDirect = TRUE, meaning the AccountContactRelation is between a Contact and its primary Account.
When I try deploying an Account record, Contact record and the AccountContactRelation record that joins them as top-level objects in the same deployment, I receive the error "INVALIDCROSSREFERENCE_KEY:You can't associate a private contact with an account.:ContactId --", presumably because in the order of operations, the Contact hasn't been updated with the Account lookup yet.
When I try splitting this into 2 deploys, deploying the AccountContactRelation alone as part of…
1 vote -
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be benefic
I would like to suggest a feature for Gearset that provides a more granular control over user permissions. Specifically, it would be beneficial to have the option to allow a user to commit changes to a branch but block their ability to create a pull request (PR). This would allow our team to review the commits before a PR is opened, providing a more effective way to manage and correct any potential issues before they impact the main repository. This is an improvement that would significantly streamline our workflow and reduce the risk of errors.
1 vote -
Download multiple objects at once from a backup run
Given the related nature of many objects within a Salesforce Org. It would be helpful to be able to filter on and select records from multiple objects in a single data download.
1 vote -
Add the ability to track who configuration changes to pipeline, CI jobs, etc...
It would be nice to see when there's a configuration was changed such as required test configuration on a CI job or pipeline configurations.
1 vote -
Changing API Version should make it obvious to save filter before CI Job can be saved
It's a usability bug, I think.
When you change the API version in a CI Job, the button to save CI Job greys out but has a spinning dial of 'Something happening'. Actually the system is doing nothing, it is waiting for the filter to be saved (even if the filter wasn't saved before) but this is completely unclear.
Changes then
1. auto-save filter or bring up the 'save filter' modal
2. Show a toast message saying "save filter"
3. Button should grey out with hover text of "save filter", no spinnerI waited longer than I care to admit,…
1 vote -
Add a link to open the deployment when a change is being promoted
The pipeline view only shows that a deployment is "running" after promoting a change. It would be useful to have a link to the deployment job and be able to view the deployment status in gearset.
1 vote -
Creating branch names from JIRA summaries can cause very long path names
Gearset automatically creates a branch name from JIRA summaries. Windows paths are limited to 260 characters.
error: cannot lock ref 'refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterio
n-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-
the-export-stage': Unable to create 'C:/Users/E19187/Repos/salesforce/.git/refs/remotes/origin/gs-pipeline/portal/SFBUS-33389/Update-Include-in-Export-formula-on-the-Intake-Criterion-object-to-prevent-Intake-Tasks-and-Intake-Document-Checklists-from-pulling-when-associated-to-a-process-that-is-not-included-in-the-export-stage.lock': Filename too long1 vote -
Update Test naming convention matching to work with implementation classes
We are using fflib and the AEP enterprise design pattern. As part of this design pattern we have interfaces and implementations for our Service layer classes. E.g. we will have something like ILumpSumService and LumpSumServiceImpl. When we create a test class it would be something like LumpSumServiceTest. So it would be great if the logic could be updated to match use cases where you have an implementation class like that. Also, I think any net new test classes added should be executed no matter what
2 votes -
Restore feature branch when a mid-flight promotion branch is restored
Have just experienced a scenario where closing a PR that is mid-flight in the pipeline caused the promotion branch and underlying feature branch to be deleted. So far, so good in terms of expected behaviour due to my pipeline settings. However, after restoring the promotion branch in order to reopen the PR and promote it in the pipeline, the next environment on the pipeline did not then show the change. This, I believe, was because restoring the promotion branch DID NOT restore the feature branch. Therefore there was no source to create a new promotion branch from in order to…
1 vote -
Create a mass back propagation button
Its very time consuming to have to back propagate one by one to each org. Please create a mass back propagation button.
Also when back propagating where more than one connection to an org exists for instance our techdebt org has several admin connections and I have to hit update on all of them. Make the back propagation smart enough to know that it only needs one update rather than on each connection to the same org
1 vote -
Feedback Search Bar
On the Feedback page place the Search bar at the top. Its odd that it sits at the bottom of the right panel
1 vote -
Grouping more than five sandboxes should not hide them
When grouping sandboxes, having more than 5 in a single group adds a scrollbar, and hides any additional sandboxes added to the group. This decreases visibility into sandbox status. I missed that there were several sandboxes that were very out of date simply because I couldn't see them on the pipeline. All sandboxes on the pipeline should be visible for visibility.
1 vote -
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to m
Please update your "Configure and deploy" option to allow the user to limit the records that will be masked in an object. We only want to mask our homeowner records in Account and Contact. We do not want to mask our dealer records. If we could limit the records that are being masked by using record types, this would enable us to use your solution. Thanks!
1 vote -
Put a "Simplify Differences" toggle at the entire comparison level instead of each item
Add the "Simplify differences" toggle to be enabled at the entire comparison level so you can filter out items that don't have any actual changes besides metadata being moved around within the xml file by the salesforce API. This way, if there are items that don't have any true differences, they can be quickly filtered out at the comparison level instead of drilling into each one and having to "simplify differences".
This would help especially with custom objects, where the salesforce api moves the Action Overrides around causing the analyzer to flag objects as different between orgs, when in reality…
2 votes -
Add an integration for Google Chat that includes an integration for Change Monitoring and Unit Testing.
Recently, it seems that Google Chat has reached some feature parity with Slack in that it has a defined integration avenue for adding notifications to Google Chat. I have found that I can set up a custom webhook to Google Chat for the CI jobs, but webhooks are not available on the other 2 features I am looking for notifications from.
I would either like to have:
a.) An integration for Google Chat with an app on the Google Chat side that we would add for the connection to our Gearset
b.) Webhook availability for more notifications, so I can…2 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 -
Allow backup job permissions to be control by Roles
Backup permissions are separate from the Roles, causing duplicate permission maintenance. Please allow backups to use Roles instead
1 vote -
Pipeline Notification for Metadata filter for Missing components
If I am committing some code via pipeline, in my feature branch that includes a metadata not present in my current CI Job filter, Can I get notified from Gearset that commited/merged metadata not present in the CI Job Filter?
1 vote -
Ability to "Hide" Sandbox Groups on Pipeline Page
In the Pipelines page, it would be very helpful if we had the ability to "hide" entire sandbox groups from view. This would make it much easier to quickly find and focus on the environments that are relevant to the logged-in user.
Ideally, this "hidden group" setting would persist across logins and page refreshes, similar to how the "collapse group" feature currently works.
I'm sure an "unhide groups" feature will be needed with this as well, in case a previously hidden group becomes relevant again.
1 vote
- Don't see your idea?