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.
1309 results found
-
Introduce Import/Export feature for Custom Filters
Expose the underlying JSON/XML for Custom Filters so that we can export it, modify it in a text editor either by hand or with python scripts, then load it back into the custom filter.
For example I have my main CI filter with 50ish metadata types, and every other filter is a subset which I establish by cloning the "master" filter and deselecting metadata types. Whenever I make a change to the master filter I am forced to nuke all the the "detail" filters and recreate them off the master using the above approach.
So many clicks. My preference would…
9 votes -
Add RecordType support for PersonAccount
Problem analyzer is always trying to remove my picklist values from any RecordTypes on PersonAccount. I am forced to use a custom "Problem analyzer template" where "Remove picklists from record type" is disabled.
Suppose I have a field called pickme: Account.Pickme--pc | Contact.Pickme--c it shows up in the record type XML as Pickme--c, and it seems like gearset tries to find a picklist on account with that exact API name, which will of course fail. My ask is that rather than raising an error at this point, GS should repeat this check on the contact object where it would find…
16 votes -
Make Custom Filters a Top-Level Menu Item
Filters are arguably the best part of gearset, especially with the support for RegEx. It is kind of a bummer that they are tucked away in a modal that can only be reached by clicking into a dropdown. Ideally you could just go to Hamburger > Metadata Deployments > Custom Filters and be routed to a dedicated page.
12 votes -
Show JIRA Title when selecting tickets to post to
As a release manager, when I go to select the JIRA tickets to associate to, I need to be able to see not just the ticket number, but also the Title to allow me to select the correct tickets without having to guess or consult another resource or use trial and error.
Currently there looks like this idea was implemented in Pipelines, but that interface is somewhat broken, and typing in the full number does not result in the ticket showing up, could use some love, but is the right idea for providing context.
1 vote -
Make Pipelines a Top-Level Menu Item
This is a less-good, but arguably easier to implement, version of my request for customizable landing pages. It takes a few clicks to get to pipelines and, since it's the place I live most often inside of Gearset these days, I'd love it if it was a menu option that is parallel to "Continuous Integration" so I could get there in fewer clicks.
4 votes -
Enable source control as source/target in Data Deployments
It would be great if we could add source control as an option for Data Deployments, this will be useful in cases where we want to backup copies of CPQ record data which manage configurations to our source control repository.
3 votes -
extend the GearSet public API to include Data deployments between Sandboxes and Scratch Orgs
Allow triggering Data deployments via the public API to eliminate having to sync data manually. This also includes triggering creation of Scratch Orgs via the Gearset API so that Gearset can instantly recognize them them.
The workflow we would like to automate is: feature branch is checked out which triggers a CI/CD system pipeline to create a corresponding scratch org, do a metadata deployment from a test sandbox, and sync data from the same test sandbox. This allows us to create on-demand full copies of the environment for purposes of E2E testing (inc. external integrations) and feature development that requires…
10 votes -
Support deployment of password and session policies via Gearset
According to the Salesforce developer link https://help.salesforce.com/s/articleView?id=000349181&type=1
Password and Session policies include a numeric code which is equal to a epoc timestamp. This timestamp will be different in each org. In order for deployment to succeed, the timestamp code in the metadata name must match the target org. Since all orgs are different, there isn't an automatic way to do this.
Please create a feature in gearset that will automatically replace the timestamp numeric code with that of the target org so that we can use gearset to deploy password and sessions policies.
2 votes -
Hide re-ordering in a Monitoring job
We have a monitoring job set up to check production changes. However, re-ordering in some components are popping up as false positive. For example, Entitlement Process and Site.com. Everyday I get an email saying # of changes have been made on production. I'd like to not see these false positives in the # so that I do not need to go to each comparison every day just to realize that it's a re-ordering issue.
12 votes -
Archiving and restore process
Data archiving for storing records that can be easily accessed when marked as archived at an off-premise location. A backup and restore would be overkill when there is a need to store only partial records or a combination of fields from records in different objects. Restoring to a new object that does not interfere with existing objects would be ideal.
1 vote -
Data Deployment Template that supports complex rules
Looking to be able to setup a Data Deployment template that supports complex rules with record limits.
For example...
- Select 100 accounts that have been modified recently that belong to division A that contain at least 1 contact, 1 opportunity and 1 activity.
- Select 100 accounts that have been modified recently that belong to division B that contain at least 1 contact, 1 opportunity and 1 activity.
- Select 100 accounts that have been modified recently that belong to division C that contain at least 1 contact, 1 opportunity and 1 activity.Currently have to build 3 or…
3 votes -
Have an ability to modify message which is posted to Slack channel.
It would be nice to have the ability to modify this notification message somehow.
E.g. include a number of PR which was merged into the main branch. Or remove extra information such number of deployed components.now it looks too big
Gearset Continuous Integration
A continuous integration run succeeded for ***** CI/CD. The job was a deployment.
Changed objects
3
New objects
0
Deleted objects
0
Source commit
1c***f2b3 votes -
Delegate Access by Comparison
Provide an additional delegate access option: be able to grant this at a comparison level to a user vs at the org level (situation is predominately experienced for Production comparisons/deployments). Granting access at an org level gives too much access (CI jobs, etc) for some users so it would be ideal to have a narrower scope.
1 vote -
See when a commit validation was deployed or not (For CI validation Jobs)
When you go to the validation only CI jobs section within the Continues Integration part we usually have a CI job targeting a prod environment, you can see all validations succeeded and the commit attached to such validation, each CI job run contains 3 options:
View comparison
View Summary
DeployThen if the validation passed and the code indeed was merged from the feature branch to the master branch (Which would have triggered the actual CI job run), how would you be able to identify wether a merged pull request was deployed or not within gearset?
For me it's very…
1 vote -
Allow for Object Deployments without subcomponents to git
When deploying an object to git currently there is no support to ONLY deploy the object metadata.
We have a large managed package that your code requires the .object file for an object in that managed package to exist for me to deploy fields or other customizations for said object git -> org. When I deploy org -> git to get the .object file into my repo it also grabs all the fields on the managed package object which I don't want/need.
I don't want the fields and I need to specifically get it from the target org because if…4 votes -
Pipeline automatic back promote
When using pipelines, it would be helpful to have the option to automatically back promote changes through the pipeline. For example, we currently have a CI job that pushes specific changes that admins are allowed to make directly in production into our master branch. We then have a Github Action that automatically merges commits to our master branch to the other branches in the pipeline, so that everything is synced. However, in order to turn on pipeline, we have to turn off our automated merge action, because pipeline creates a bunch of PRs when the automation runs. This forces someone…
6 votes -
Customize CI job commit message
When a CI job pushes changes to source control, it always uses the message "CI deployment from job <CI job name>". It would be very helpful to be able to customize this message.
5 votes -
change monitoring for scratch orgs
The Change Monitoring feature only supports normal orgs (sandbox, developer, prod). It does not support scratch orgs
For use cases where developers inadvertently let their scratch org expire with pending, uncommitted work, it would be nice to recover the work before and after the scratch org expires
2 votes -
View on GitHub for custom git repository
Offer the option to "View on GitHub" for custom git repositories in Commit successful screen
1 vote -
BitBucket commit on a successful Org deployment
It would be a nice feature to have a setting on the deployment summary page to also commit to a git branch with deploying to an org.
2 votes
- Don't see your idea?