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.
1244 results found
-
1 vote
-
Ability to cherry pick changes in a file
When comparing changes between a source org and a target org for a given file/metadata component, it will be great to have the ability to choose which change(s) should be promoted from the source org to the target org.
Presently, it's an all-or-nothing scenario i.e. either one deploys all the changes to a given file from source to target or deploys none. As a workaround, we cherry pick changes to a file using VSCode and then deploy to the target org using VSCode –– which is the exception to our "all metadata changes must be deployed through Gearset" policy.
Adding…
5 votes -
Add support for deploying a name change to a SFDC component (such as profile)
We occasionally change profile names during permssions clean-up projects. Currently, when you deploy a profile with a changed name, Gearset recognizes it as a "new" and a "deleted" profile, instead of a single "changed" component, which makes the deployment challenging.
I know that the name is used as an identifier, since the Id may not always match between source and target. However, if you add support for this, the tool could try to identify components with name changes by looking for the same Id in source and target with a changed name.
2 votes -
Ability to choose whether or not to respect the forceignore file
Would like a checkbox on the comparison screen that allows me to choose whether or not the comparison will respect the contents of the forceignore file. (Similar to the checkbox allowing you to choose whether or not the comparison should use the package.xml file).
Our usage of Gearset does not align with our usage of the forceignore file for automated deployments. In fact, we often use Gearset to manually compare and/or deploy items that we specifically ignore for automated deployments.
Summary of problem this new feature has introduced:
We use gearset for org -> git deployments, and for git ->…5 votes -
Added an 'Or' function to the Filter Options
Right now there is only an 'And' filter when configuring Fields on the same object. It would make this much more powerful of a tool if we were able to chose between 'And' & 'Or'.
4 votes -
add the ability to change columns in the compare results page.
Use Case:
When deploying items from one Org to another I need to filter by newly created items as well as latest modified items. So there is a use case here to add the Created By and Created On columns in the Compare window.Or the ability to add predefined columns into the view.
1 vote -
Add a batch size option directly on Data Deployment and Data Templates
Currently we can specify the batch size for bulk data loads on Account level.
With this kind of setup we can't have two pararell jobs running on different batch sizes and we also need to memorize what batch size is required for each of my Data Templates.
It would be nice if we could do that directly on Data Deployment job and even save such setting in a Data Template.
1 vote -
Allow CI jobs to validate PRs of a branch into Separate Scratch Orgs
Currently CI jobs can only validate PRs into a regular org. So if you have multiple PRs raised to that branch then you have to wait as they each run one after the other. If we could validate into separate Scratch Orgs instead then all the PR validations could run in parallel and it would speed up validation
6 votes -
Validation Job to validate feature/* branch by scratch org creation
The idea is to validate feature branches in repo. For doing this it's necessary to allow specifying source branch by pattern (like feature/*) in "Add CI validation job" menu. The validation should check whether the code breaks the scratch org creation or not. This is valuable due to fragility of scratch org creation process (sfdx force:source:push).
5 votes -
'Select All' on Draft Deployments and Deployment History
When combining packages it would be very nice if there was a 'Select All' checkbox.
1 vote -
Allow Source to choose multiple Branch for CICD Validate/Deploy
when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD
2 votes -
Jira ticket association should carry over to deployment merges and comparison refreshes
If I clone a deployment, it copies all the associated Jira tickets, but if I merge two deployments, the list of associated Jira tickets is empty. Is that how it is supposed to work? I would expect a union of the lists of all the merged deployments.
The same would apply to comparison refreshes.
1 vote -
WebStoreTemplate
Please add WebStoreTemplate as a metadata type
1 vote -
Users should be able to specify test classes and save them to draft deployments
Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.
also when deploys are combined, they would get all the test classes, again, saving lots of time.
6 votes -
Jira: Ability to pass a list of Jira ticket Ids vs. single entry
Would really benefit from being able to paste a list of Jira Ids, e.g. comma-delimited (similar to specified tests) on final deployment. Hate giving up validation / deployment status writebacks to Jira, but often we have packages spanning dozens of Jira tickets and entry can be time-consuming, especially if there is a failure or refresh needed and Jira ticket associations get lost from the draft.
1 vote -
To be able to filter within a dropdown
https://ej2.syncfusion.com/vue/documentation/drop-down-list/filtering/
Much like the above, when searching through many fields it can be tedious1 vote -
Add Analyzer to Warn/Remove Named Credentials with Passwords
Currently, attempting to deploy a named credential will fail as a "password is required for the specified authentication protocol".
This can mean manual work if you have a lot of CI deployment jobs to sandboxes or annoyance if you expected to be able to deploy it.
It'd be great if an analyzer existed that would alert/warn the user about it going to fail and unable to be deployed (suggest removing it from the package)
5 votes -
Detailed monitor reports to inbox
Opening the Monitor reports in Gearset is very time consuming. I would like a daily report to arrive in my inbox with the Changed, New or Deleted object names, Data Changed and Who.
1 vote -
Bash scripting
Add support for bash scripting. This is one of the most powerful features of Jenkins and something that would make a huge difference in Gearset.
5 votes -
Allow invited people to replicate data and metadata from Backup job
Allow the ability to replicate data and metadata for persons with full permissions to a backup job even if they did not create the backup job
With several administrators for a Salesforce organization, the objective with a backup is that in case of an emergency or error it can be fixed within a short period of time to avoid downtime. The backup job allows us to have a copy of our data, but it would also be great if we could have a copy of the person who is responsible for the backup. With just one person being able to…
1 vote
- Don't see your idea?