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.
1301 results found
-
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 -
Deploy SOAP APIs like Permissionset assignment
I am able to deploy profile components and permission sets separately. But the permission set assignment is part of salesforce SOAP API and I couldn't deploy the same using GearSet.
Kindly provide deployment options not only for Metadata API, also SOAP APIs3 votes -
2 votes
-
Attach pdf items details in the email notif "Your organization has changed"
When you receive a notification concerning a change into an organization you need to know quickly which items are changed.
4 votes -
Add the option to note successfully deployed components in CI notifications
When a CI job is configured to post to slack, and a job fails, it is very useful to see the message posted with information about what failed (error message, number of components that failed).
However, when a CI job succeeds, it only shows the counts of changed/new/deleted objects.
It would be very useful to have the option to list out what was deployed - this would make it easier for devs/qa users who monitor these slack notifications to understand which deployments are relevant to them at a glance.
2 votes -
Pulling object dependencies during data backup
A cool feature would be the ability for Data backup to have the ability to select object dependencies when you select a particular object for instances where you want to backup a subset of data and not just your entire org
2 votes -
Display a custom name in Salesforce when deploying from Gearset
When we deploy a change to one of our Salesforce orgs using gearset, the name that is displayed in the "Deployment Status" in Salesforce is an ID. It would be helpful to display the name that we entered in Gearset instead of the ID so that we can easily identify the changes when looking at them in Salesforce
5 votesHi,
We have recently investigated adding this feature again, but unfortunately Salesforce still don’t seem to support being able to display custom names via the Api (or it’s a feature that’s not well documented). There are requests for adding this ability via:
https://success.salesforce.com/ideaView?id=08730000000cJdxAAE
If the situation changes then we’ll certainly revisit this. We’ll keep this post opened for other users to also add their votes but it’s currently out of our hands as to when or if it can be added.
Regards,
The Gearset Team
-
Only display active branches when displaying branches from a bit bucket cloud repository
Only display active branches when displaying branches from a bit bucket cloud repository
5 votes -
Improve the UI around deployment objects dependent on objects not in the comparison
Deployment of certain types of objects requires that other objects on which they are dependent be included in the deployment. If the needed objects have not been included in the selected items and they are not part of the comparison, Gearset will display the following message:
Problem: Some itmes reference componnents that were not downloaded from either the source or the target.
Solution: Removing the elements that reference missing components from the affected items will make the deployment more likely to succeed.
Below this is displayed a table with a column of checkboxes at the left and three additional columns:…
1 vote -
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 -
allow a method to set up default branches.
I frequently deploy from our on premises GitLab repo. It would be great to have the ability to set the default branch it goes to. It would be one less click for repetitive steps
5 votes -
Support VS Code extension: ForceCode
Can you please support VS Code extension (ForceCode) source format so that we can use the extension to commit and include in CI jobs.
1 vote -
Add an option to share orgs by default
Where we have a developer-manager, and a team of developers, it would be useful to be able to have a default for sharing org-connections where the manager always has access to their team's orgs.
At the moment, we have to share each org one-by-one.
This has caught us out where a dev team member validated a deployment, then went on holiday thinking that we could deploy it for them. They forgot to share the org-access, so we had to recreate the deployment to get it done.
2 votes -
Mark items as already reviewed earlier
Today we are gearing up for a major deploy so we are deploying many different changes into gitHub. It would be nice to be able to mark whole sections of content as already reviewed such that any new comparison could ignore all of that content. Then we could look at only the new or newly changed/deleted content.
2 votes -
Display "No Difference" metadata sources on Deployment Summary page
On the "Deployment Summary Page" it would be great to add a column to the list of metadata components added which shows for the "No Difference" items showing the source piece(s) of metadata which is causing this "No Difference" to be included.
This would dramatically help in the narrowing down of why a piece of metadata is included - especially if that piece of "No Difference" is a managed package and cannot be altered. In a large deployment, trying to identify a root cause for why a component was added is quite difficult. Simply giving a way to track back…
1 vote -
Email2Case Deployment for Selected Email2Case Setting
When deploying email2Case i am unable to choose particular email2Case that i need to deploy and end up choose all the email to case settings. Needed feature to deploy this selectively.
1 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 -
Add Upload CSV functionality to create an upload template for CPQ deployments
For CPQ Deployments add an "Upload from CSV" feature where a user could upload a file with specific External IDs across multiple objects to tell Gearset what to migrate in a single click.
For example, the user could list the Object API name in Column A of the sheet and the External ID in column B and then Gearset would parse this and create a Data Deployment based off of those records specifically. This would be incredibly useful for any CPQ deployment where you need to only deploy specific records not the entire object!
8 votes -
Plain text list export of metadata
There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.
1 vote -
Allow complex filters and child relationships on filters for data loading
Allow complex filters and child relationships on filters for data loading. For example, filter the Account to only load if the Owner is an Active user in the system.
12 votes
- Don't see your idea?