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.
1339 results found
-
Display the developer who opened the PR throughout the entire pipeline flow.
As a Release Manager, I have difficulties identifying the developer responsible for the PR.
The developer's name only appears when they open the PR at the beginning of the process, and in the following stages, it shows the system user's name from git that Gearset uses to open the PRs up to production.
Since I need to easily know who opened the PR during the release creation, I have to open the feature card to find the developer. ...
1 vote -
Enable multiple orgs to act as build agents for single pipeline step
Occasionally our queue is backed up waiting for dozens of PR's to validate, this happens because a single org can only validate one PR at a time. It would be helpful for a solution that allows us to attach multiple orgs (sandboxes or scratch orgs) to a pipeline step such that multiple PR's could be validated in parallel. Then when a PR is deployed it could easily be deployed to all of the attached orgs.
1 vote -
Solution for enabling parallel builds validations, i.e. multiple build agents
Occasionally we have a backup in our queue PR validations where dozens of tickets all have to individually wait for there spot in line to validate. It would be great if we could spin up multiple orgs (sandboxes or scratch orgs) and attach them to a single pipeline element such that each org could help load-level the validation queue.
1 vote -
Preserve Precision Selections through Fetching the Latest
You're precision selections feature is absolutely amazing! Every time I use your tool it just gets better and better and this feature has me hooked. It's been huge with lightning web pages which often have multiple changes in UAT and need to be separated for deployment.
We prep deployments before sending to UAT. Occassionally, there has been a big delay since the package was originally validated. If I need to go back to the original draft deployment and refresh the selected items to ensure I'm not overwriting something else that went out, the precision selections are cleared.
- There is a…
1 vote -
allow us to automate the PR Syncs after a shedule deployment occurs
due to drift occurring because of the environments being out of sync after a deployment occurs I would love the capability to scheduel an automated PR sync after a successful scheduled release deployment occurs. like a checkmark box on a per sscheduled deployment basis.
1 vote -
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 -
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 -
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 -
Please add support for decomposeCustomLabelsBeta
Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm
11 votes -
Stop Off-setting Partial Selections when a Package is 'Fetched' for the Latest
Hi,
Our team creates individual draft deployment packages and then we consolidate it into one package and fetch for the latest before validating. In some of our individual draft deployment packages we are selecting partial changes to a page layout or a lightning record page but it is off-setting this partial change and we are given the prompt: 'Precision selections have been reset for these items'. Is there a way we can fetch for the latest without off-setting these partial changes?
Thanks!
2 votes -
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 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
- Don't see your idea?