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.
1332 results found
-
Enable Excel export of org differences—profiles, permission sets, and objects—in the same side-by-side format with change indicators
I compared two profiles from different orgs—specifically, the old and new environments of the same company—to identify any differences and present them to the client for review and approval of necessary changes in the new org. However, I was unable to export the comparison results into Excel. It would be extremely helpful to have the ability to export the comparison data in the same structured and visual format as shown in the Gearset comparison window, making it easier to review and share with stakeholders.
1 vote -
Make components searchable across features in the pipeline
If I know the name of a component, Can you give me a way of searching through the pipeline to see what features it resides in, where they are and when it was deployed please
1 vote -
Deployment Failures in Pipeline
The flow of a pipeline promotion is as such:
- Validate deployment to org
- (on success) Merge PR into base branch AND move PR to "Recent Promotion History" tab
- Deploy to org
IF the deployment fails at that point, or is partially successful it would be great to denote that somewhere within the CI job within the pipeline. This would give the devs.admins more visibility into the true state of their features. Maybe we don't even move to the next environment until after a successful deployment.
1 vote -
Provide a visual indicator on upstream systems when out of sync with master
Often times we see drift items added to PR's in our upstream systems. It would be nice to have an indicator that shows if a static branch is out of sync with master.
1 vote -
Automate upstream branch syncing
After merging/deploying to prod allow auto-creation of sync PR's to upstream branches/orgs (QA, UAT, Staging, etc...). If the sync PR's could be promoted automatically that would be amazing.
2 votes -
Automatically Backfill Dev Environments with Pull Request When Changes Are Promoted Downstream
Description:
Currently, Gearset’s pipeline tool does a great job of back-propagating changes between static environments when a change is made further down the pipeline. However, this behavior does not extend to developer environments, even if the change originated from a feature branch tied to that dev environment.Problem:
If a developer starts work on a branch in their dev environment, and then that branch is promoted down the pipeline (e.g., through UAT, Staging, etc.), and changes are made to the branch further down (e.g., hotfixes, last-minute edits), those updates do not automatically get proposed back to the original dev environment.…
1 vote -
Add Monday.com as a source for User Stories
Add Monday.com as a source for user story integration
1 vote -
Add spell checker to CI/CD pipeline
Spell checker helps maintain a high standard of accuracy, ensuring your content is reviewed in initial PR's itself. Just like how we use Clayton code feedback.
If typos is in customer facing texts in UI (which is can be a big problem in public facing application where large no of users visits.)
It would be good if spell checker can be added as a policy inside Clayton. So that we can find and fix issues easily.
Advantages
* We can also prevent potential PROD P1 errors.
* Enhanced Code Quality
* Improved Deployment Efficiency
* Reduced Technical Debt5 votes -
Enhancement Proposal: De-merge Option for Gearset Branch Management
Currently, Gearset provides a helpful feature to merge branches, which is ideal for creating a Release branch that bundles all related components. However, it would be a valuable enhancement to introduce a de-merge or selective unmerge capability. This would allow teams to easily remove specific feature branches from a Release branch particularly useful in scenarios where some stories are pending approval or need to be excluded from the release at the last minute.
Such a feature would improve flexibility during final release preparation and reduce the need for manual branch adjustments or rework.1 vote -
Deploy CustomLabel by label separately
The automated deploy (CI) filter does not have the resources to deploy isolated CustomLabels, so that specific labels can be included or excluded.
1 vote -
Delete Flow by Version Number
It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:
You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.
You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the…
1 vote -
Add folders to Data Deployments for better organization
To help with organizing data deployment templates it would be great to have some sort of folder structure to allow us to group data deployments by team. We have several Salesforce Teams at my company and we all have slightly different data deployment needs. It would be great to have team folders for data deployment templates...for example Sales Team Templates, Service Team Templates, Marketing Team Templates, etc. Today we use some naming conventions which is fine, but would be a little cleaner if we had a folder structure. Thanks for your consideration.
1 vote -
load more items
Please stop using "Load more items..." as the way to load more table items. It's very annoying to have to say show me the last 30 days but then click the button 20 times to get there.
I'm referring to the Promotion history page but anywhere this concept is used should be ripped out.
1 vote -
Add a feature to ignore queue members when deploying queues
When deploying Queues with Gearset the members section is automatically included and the member list is deployed to the target org. Gearset has a suggested fix to sync the queue members with the target environment but it doesn't always work.
Salesforce supports deploying queues with an empty list of users as queue members are more like data than metadata I suggest a feature toggle in Gearset where the users section of the queue is ignored for deployments to preserve the user list in the destination org.
Our company and many others probably maintain the queue users directly in production as…4 votes -
give personal settings
personal settings to adjust the following:
auto populate deployment notes from feature branch over to the pull request deployment notes on create pull request screen
auto set checkboxes on create pull request screen (skip CI validation checkbox etc etc)
set default target branch other than main branch on create pull request screen1 vote -
View webhook pipeline settings and error history even when promoting
When any pipeline is promoting most of the options in the pipeline settings menu are disabled, e.g. 'View Webhook Errors'.
We want to be able to access these features, as we might need to reference a webhook error, and not have to wait until the pipeline is finished promoting. Our team is promoting at least one feature to one pipeline most of the day so we have to wait until after business hours to reliably access this information.
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 -
Enable use of multiple parent filters under 'Filter using parent object' in data deploys
When the “Only deploy (object name) records that are children of the (dropdown of selectable objects) records that are being deployed.” checkbox is selected on the Account object settings screen of a data deploy, only one parent record can be selected. The ability to filter by multiple fields would be useful in my org.
Use case: we have a custom object Beneficiaryc with lookups to 2 different objects: Asset_Groupc and FinancialAccountc. AssetGroupc and Financial_Accountc are both children of the Account object, so I’m able in one deploy to include Account records with all…1 vote -
I would like the ability to auto promote updates to inflight feature branches
When using feature branch promotion in pipelines, I often find myself in a scenario where I’ve pulled a new feature through the pipeline to one of my static environments. I then test it, discover something that needs to be changed, make the change in the dev environment, and pull that change through the pipeline again so it reaches the same static environment for retesting.
I would like functionality that enables me to release a new change to that branch from dev and have it automatically promote through all static environments, stopping at the current one where the original pull request…
1 vote -
add preview of archived files and let admin choose fields to show on the related list in Archive Viewer
Please improve Archive Viewer with a preview of the files Archived, like the current document viewer on SF and consider to add more functionalities on the related list shown on Archive Viewer, like choosing fields to show and search bar incorporated.
These functionalities are already available with other Archive apps connected to SF.
Let users select the record to restore directly from the related list in Salesforce.1 vote
- Don't see your idea?