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.
347 results found
-
Add omni components to filters through metadata API
Now that Salesforce has moved omnistudio into standard runtime (as opposed to managed package) and also added the omnistudio components to the metadata API, the following components:
omniDataTransform
omniIntegrationProcedure
omniScript
omniUiCardSince these components are in xml format, it is much easier to see differences in source control.
It also removes the need to perform separate deployments for the Salesforce metadata API and the vlocity build tool.7 votes -
1 vote
-
Webhook errors page does not have a scroll bar
Firstly, thank you for adding the Webhook errors page! This surely will help us troubleshoot webhook issues. However, I am having an issue viewing the page.
Steps to reproduce:
Using Chrome or Edge, Windows 10
Pipeline > Gear Icon > View Webhook Errors > Observe that there is no scroll bar on the side of the page, nor does scrolling with mouse work as expected, yet there's clearly additional rows partially displayed.1 voteHey,
As of 3rd of April 14:00 UTC time, this has been fixed.
Thanks again,
Gearset Team
-
On the new Flow Comparison, goto connections incorrectly display as "End"
When seeing the changes in a flow in the new graphic comparison, there are connections which are incorrectly displayed as the flow ending
1 vote -
Improve the doc page: Fixing a feature that’s halfway through the pipeline
The procedure as written seems complex and counter-intuitive
Given that a developer sees the process as DEV->Integration->UAT, if an error is detected in UAT manual or automated testing, the fix should flow from DEV -> integration -> UAT.
But the article has the fix going from DEV->UAT and then back propagations back to Integration plus manual PRs created in VCS. This seems way too complicated and hard to understand for a mere admin or junior dev
1 vote -
Add to Flow Navigator the flow version description
It would be very handy if the new Flow Navigator view was able to display flow version description. We update this frequently to describe new changes, so being able to read this documentation in the Flow Navigator would be helpful to understanding the flow.
Adding this either as a banner along the top (like some flow xml views) or as an element in the navigator sidebar would be acceptable.1 voteYou can find the Flow description under "Settings" in the Flow Navigator sidebar
-
'View and Resolve Conflicts' button should open in a new tab
More of a UX enhancement than a bug but not sure where else to put this. From a PR in the pipeline, the 'View and Resolve Conflicts' does not allow me to open the page in a new tab (tried Chrome and Edge). It would improve my workflow quite a bit if it opened in a new tab by default, or at least gave me the option to right-click open in a new tab. The conflicts take a while to load and I almost always have something else to look at on the CI pipeline page while the conflicts are…
1 voteWe've made a change so that you can right click the "View and resolve conflicts" button to open the page in a new tab.
-
Add ability to precision deploy custom applications and all other file types
The ability to select specific lines in files for deployments is crucial for org and project management, and should be expanded to all file types. For example it currently is not possible to only deploy a new tab in a custom application, without deploying all other changes in that custom app, which is not manageable with multiple projects/updates being worked on that application concurrently.
5 votesWe've added precision deployments for Custom Applications 🎉
Please get in touch if there's any specific metadata types that you'd like to see in precision deployments.
-
Allow automatic tagging of release commits
I've found it very useful to be able to quickly identify release merge commits from our VCS. Being able to search for a tag in our VCS would allow us to easily compare one version to another without having to use something like git bisect. I'd like the option to automatically tag a commit (you could probably use the release name) would be helpful.
2 votesGearset will automatically tag pipeline releases with the release name. For more information check our documentation.
-
MetaData Type for BatchProcessJobDefinition missing
The MetaDataType for BatchProcessJobDefinition is missing from GearSet's list.
Need this added to allow us to deploy Batch Process Job Definitions between environments.1 voteThis was released 10th November 2023
-
Support OmniSupervisorConfig Metadata Type
Can you please support OmniSupervisorConfig metadata type that was introduced in Spring '23 (API v57.0) as per the official documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_omnisupervisorconfig.htm
1 vote -
Option to exclude all custom fields during data deployment
Hi, We are doing data deployment from one production org to another production org and we have completed the migration of all records of a particular custom object but after completion of record migration the client wanted to migrate the files and attachments present in the records.
while doing so we do need to update all custom fields present in the records again as this could replace the updated records with old data from old production.
So we have used the exclude fields option but there is no option to select exclude all fields at a time we have to…
1 voteLive in the app as of 8th June 2023.
-
Partial environment variable replacement and wildcards
Some types of metadata, such as Platform Event Subscriber Configuration, have attributes identifying a user by username. As such, regardless of the value in the source environment, the value deployed to the target org must match the username pattern of that org.
For example, if the value in the source repo is <user>name@example.com</user>, when deployed to a sandbox, it must be <user>name@example.com.sandbox1</user>. From sandbox to sandbox: <user>name@example.com.sandbox1</user> must become <user>name@example.com.sandbox2</user>. And finally, when going from sandbox to production: <user>name@example.com.sandbox1</user> to <user>name@example.com</user>.
This could be solved by supporting environment…
6 votesYou can now use Regular expressions in the "Find what" field when defining environment variables, allowing you to do wildcard/partial replacements.
-
Precision Deployments for Lead Convert Settings
Precision Deployment is currently not enabled for lead convert settings metadata. 2 orgs may have different lead convert settings or we may not want to migrate all the mappings from one to other. Hence, this is a must have.
1 voteWe've added precision deployments for Lead Convert Settings 🎉
Please get in touch if there's any other metadata types that you'd like to see in precision deployments.
-
Refresh Comparison enhancements
When doing a "Refresh Comparison", allow only refreshing the source. Or to only refresh the selected items from the source and/or target.
Example, deploying from a git branch to a sandbox, refreshing the metadata takes a few seconds from git, several minutes from the sandbox (target).3 votesWhile not exactly one-to-one match, we think this UserVoice already delivers the desired outcome:
Thank you for upvoting this UserVoice request!
-
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues
I would like the option to view the delta CI only changes within the comparison, like the agents who are helping me untangle issues. ask kevin slattery to show you.
3 votes -
Add schedule deployment for Pipelines
It would be great to add a new feature to cherry pick and schedule deployment for the changes that have reached up till staging/uat and should be released to Prod. Without this feature it becomes difficult to manage releases to avoid downtime.
7 votesYou can now schedule deployment for a release in Pipelines.
-
support blank values and/or regex in the "Find What" field on Environment Variables
...support blank values and/or regex in the "Find What" field on Environment Variables.
I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.
5 votesYou can now use Regular Expressions with Environment variables.
Simply enter the regex value in the "Find what" field and tick the "Regex" checkbox before hitting "Add environment variable" button.
Thank you for submitting the requests.
-
Multiple metadata comparison filter selection
Having multiple comparison filters to target specific metadata is handy but sometimes you need some additional components for a deployment (e.g Flow & Custom Fields).
The ability to select more than one metadata comparison filter would be a great help and would save on the number of custom filters created and shared.
4 votesWe have now made it possible to add components as needed to a comparison. Please check out our announcement on it here for more details and a short demo - thanks!
-
Deleted matching rule not showing as difference when trying to commit
The deleted matching rule is shown as 'deleted' in the comparison but when trying to commit and moving to the overview screen it is shown as 'no difference' which makes it impossible to commit.
6 votesThanks for reporting this bug. A fix for this was released on the 30th June. You should no longer have any issues when trying to deploy deletions of the various "...Rules" types
- Don't see your idea?