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.
1348 results found
-
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 -
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 -
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 -
Using Back Promotion for single Environments only and selective PR's only
We normally update our developer orgs with the "update sync" function after the PROD release. However, sometimes we have changes that are build on top of each other but developed by multiple devs and therefore orgs.
In that cases, it would be nice to turn on "back promotion" but only for certain environments where it is needed and not globaly. In addition, being able to selectively create back promotions for PRs would be nice as well.
At the moment, if the feature is activated, Gearset is creating a back promotion for every PR, regardless if it is needed or not.…
1 vote -
Select All PRs for promotion
When promoting PRs from one environment to another in the pipeline, it would be useful to have a "Select All" option
1 vote -
Show duration for comparison jobs
While the Comparison History screen shows when a comparison job was initiated, it would be extremely helpful to display the duration of that comparison job, from when it was initiated, to when it was completed.
Ideally, this would show on the Comparison History screen, and/or on the actual Comparison screen itself after it was completed.
2 votes -
Have the ability to see the metadata comparison between a merge-branch and the destination environment in Pipelines
Greetings,
I would like to request the ability to see the metadata comparison between a merge-branch and the destination environment.
For example, my pipeline is setup:
Developer's sandbox --> QA sandbox --> UAT sandbox --> Production
with the repository branches (merge-branch) for each sandbox respectively:
merge-QA
merge-UAT
mainAfter a feature-branch passes its validation and is merged into the merge-QA, I would like to be able to see the metadata comparison of what is about to get deployed to the 'QA sandbox'. We have the ability to see the contents of the commit via the link to our repository hosting…
1 vote -
Flow Navigator, show more information in Settings (Trigger Order, Status)
within the Settings Section, please show more data
Absolutely missing: Trigger Order (It is compared in the XML)
Label (Currently Interview Label is shown, but that can be different from Label, we need both)
ProcessTypeOthers?
1 vote -
Make pre/post deployment steps conditional on developer sandboxes.
Pre/Post deployment notes can be set to pertains to various static environments but they always apply to sandboxes after a back deploy. This should be conditional-- most of the time I only set them applicable to prod and they aren't applicable to developer sandboxes.
3 votes -
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…
1 vote -
Improve UI of Analyser, 'Some items reference components that aren't in the target'
This analyser, does provide suggestions on metadata items to be included, but it does not mention the why.
Today I got the suggestion to include something, which I had no intent to include, but I could not find WHY, Gearset would like me to add this to the deploy.
Providing the reason, makes it easier to adjust the deployment, maybe remove an item, or uncheck something I accidently added to the deployment.
1 vote
- Don't see your idea?