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.
1380 results found
-
Autodeploy on git branch a successfully manual deployment on org
When a developper deploy a new feature on a sandbox it will be perfect if the deployment can be auto deploy on a branch git (and copy the deployement note, etc).
Today I use a CI job backup on the sandbox but we lost the deployment comment + the updates granulartity.
We could use also the "Clone Button" on the result deployment page but it's lost time to relaunch the comparison and the different step etc while we want exactly replicate the deployment.
1 vote -
When validation fails, allow option to automatically remove metadata from deployment that was causing failure
It's not convenient when a validation fails, to then download the excel file of the the validation errors, view in separately form Gearset, and then go through the list of metadata I'm trying to deploy and try to uncheck each one that failed the validation. It would be nice if Gearset did that for me.
14 votes -
Add an option to disable deploying the email to case settings in Case.settings
This will allow to deploy Case.settings without getting this deploy error:
EmailToCaseRoutingAddress[Info]: emailServicesAddress is a read only field and cannot be changed2 votes -
When CI jobs fail with "admin operation already in progress", retry the CI job automatically
I was informed in my slack integration today that my CI job failed with an error message of UNKNOWN_EXCEPTION: admin operation already in progress See https://app.gearset.com/failed...
I would like to see Gearset automatically identify this type of error as something different than a metadata error and then retry that CI job 3 times over the next 90 minutes (for example). It would be fine for it to stop after those 3 successive failures.
1 vote -
Allow for selecting/unselecting Filter by Package.xml
When doing a clone or a refresh comparison today the ability does not exist to add or remove the option of whether you are filtering by package.xml. I would like to see this added.
For us what might occur at times is that we have a release occur where this is accidentally selected and we find that a number of items are missing and due to this being selected. We have no way to remove the selection and have ended up starting over. One of a number of scenarios where it would be nice to have the option to do…
2 votes -
Allow us to personalize the report generated at the end of the deployment
I want to send the automatic report generated at the end of the deployment to my client. However, I want to personalize it with the logo of my company or add additional text.
6 votes -
1 vote
-
Warn the user of unsaved changes to an org compare filter
It would be nice if we got a warning if we have selected specific components in a filter but havent saved the filter when we hit OK. I've lost a lot of work on a custom filter because I forgot to hit 'Save' - I would have thought it would auto-save when you hit OK.
2 votes -
Provide the ability to run static code analysis on all commits to the repo
We'd like the ability to run static code analysis on all commits to a repo, regardless of the branch name. This would allow us to catch code quality issues early and up front, regardless of the branching model we use.
Example: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow (development is done in feature-* branches, so there's no one branch we can configure a CI job on)
1 vote -
Allow optional parameters to the GearSet login url to support login method and custom domains if needed
When using Salesforce logins along with a custom domain, the current gearset login process requires 6 steps:
- go to https://gearset.com/
- Click "Log in" in upper right
- On the "Welcome back screen", click "Salesforce (Production, Developer)"
- On the Salesforce Login page, click "Use Custom Domain"
- Enter "customdomain" and click "Continue"
- Enter Salesforce Production Username and Password
If the GearSet login URL (from step 2) https://app.gearset.com allowed for optional parameters, a couple of the above steps could be eliminated
An example URL might be:
https://app.gearset.com?loginMethod=sfProdDev&customDomain=customDomain
or
Then that URL with the params could be saved as a favorite or placed in…
3 votes -
Gearset to do Sanbox Refresh by copying metadata and data from production
Quite often an Environment needs to be refreshed, but every time it happens all the integration breaks as OrgId changes. Gearset can move metadata and data, which when made together can be a solution for sandbox refresh. Full copy sandbox sometimes takes days, GS will be able to it quite quickly.
1 vote -
Namespace Mapping for Managed Packages
We are an ISV partner with a managed package we sell to lots of customers. That means our package is namespaced. However with a distributed development team and multiple dev orgs, all source code is not namespaced, and is maintained in source control (github) without namespaces. Only upon unit test and promotion to the package org, does the namespace get added. This results in two basic problems (and others). 1) comparisons between unit test and package result in almost everything being flagged as "changed" due to the namespace, and 2) all aura components are always flagged as "new" when they…
7 votes -
Set time on CI Jobs instead of running every 4 hours or 24 hours
Is it possible to set time Instead of running CI Jobs every 4 hours or 24 hours.
22 votes -
Preserve auto-number field values during a data deployment
Staging environments typically exist with integrations with other systems that have references to auto-number fields
Data deployment re-evaluates auto-number fields instead of keeping the values of the source.If data deployment jobs could automate the following it would probably work
1. changing the type of the auto-number field to text in the target org
2. potentially removing apex references to the field
3. deploying the data
4. rolling back metadata modifications in steps 1 and 21 vote -
Ability to update value of Reference field for a data deployment
"Select reference fields to deploy"
Ability to edit the value for the target deployment data for the reference field instead of searching for the match on the Target.
Ex. Loading Opportunities from a Source to a Target that contains 5 different record types, but when uploaded to the Target we specify the recordtypeid to one that matches a recordtypeid on the Target for the entire data load.
Similar to how the Owner reference can ignore the Target's users and default to the running user of the data deployment.
3 votes -
Ability to have Tests to Run during Validation to default to Unchecked all
Ability to have Tests to Run during Validation to default to Unchecked all vs all checked (even before they finish loading into the component). We often validate with only a few tests or predefined group of test classes that we input into 'Specify Tests to run' and if a user inputs those test classes in the text area before all the Tests populate above in the list, it will include all of the ones available. It defaults to checked all and they need to remember to uncheck them or to wait for them all to load which can take awhile…
3 votes -
Create an rss or atom feed as you add new features
When working inside of Gearset, it often alerts you to changes that have been recently made. It would be nice to have these as a separate, consumable, feed. We have a slack channel that we would like to pipe those changes to, for instance.
2 votes -
Add possibility to save custom filter RegEx for subcomponents
If you want to deploy new fields and field level security, I want to create a custom filter that hides all profile setting except of field level security and make that custom filter reusable.
Unfortunately RegEx only works on top level elements. In this case profile names. That doesn't make sense since that would hide field level security too.29 votes -
View Grouped Successful, Validated, and Monitor Jobs per Instance in List
Our organization has now done over 13,000 deployments (yay!), but that means when I have to search for past deployments, any searching beyond 10 days as the filter becomes an impossible task because of the sheer volume that has to be searched (boo).
When trying to combine successfully deployed packages into a new package, if I have to change the date range to find a deployment done several months ago, I lose the selected deployments from a more recent timeframe and can't select them all to combine neatly.
If we could see successful deployments by viewing the authorized Org in…
10 votes -
Selectively filter managed package metadata without excluding unpackaged components
Add the ability to filter in/out managed package elements from a comparison set at metadata type level. e.g. allow for the comparison of managed package objects and fields but exclude other managed package metadata types whilst allowing those types to be available for non-packaged constituents. More specifically for instance, exclude manage package page layouts and include managed package custom fields whilst including both unpackaged page layouts and custom fields in the comparison set.
The reason for this is to minimise the comparison set which can reach limits due to size whilst including all mandatory metadata elements for a deploy.
Using…
4 votes
- Don't see your idea?