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.
293 results found
-
Combine validated packages
Hi Team,
Please add checkbox for validated package as same as deployed ones. that way I can combine package even for validated one's and deploy.
10 votes -
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 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 -
Do not add Pre/Post Deployment if there is no value.
The current behavior is when the developer do not have any Pre/Post deployment steps added in his/her PR even though Gearset adds the comment in VCS and Jira, and as a result, it creates lots of noise.
Gearset: Deployment steps for UAT1 #4062 (do not edit)
Pre-deployment steps
TitleCompleted at
Completed by
Post-deployment steps
TitleCompleted at
Completed by
7 votes -
Remove "No Difference" items when commenting on jira tickets
when i connect a jira ticket to a commit, I like the way gearset posts a comment on the jira ticket listing the changed items. what I dont like is the long list of "no difference" items posted on the ticket. It makes the ticket comments super long and annoying to scroll through. can gearset update this to only post the difference metadatas, or at least give us the option to include or exclude
7 votes -
Get Notified if Pull Requests or Validation Fails
Our Org has Gearset Officers who handle promotions. It happens at times that I create a pull request and have it start validating (which can take a while). I'll navigate away from the screen and totally forget about it, assuming it'll get pushed to the next environment.
But sometimes there are merge conflicts, or validation fails. I'd love to get a notification, either in email, or as an integration to an attached jira ticket that it failed. That way ill be notified by slack or whatever.
Just an addendum here. We use 3 environments. Admin, UAT, and finally Production. When…
7 votes -
Incorporate Relationship Graph into metadata deployment
Right now is it not possible to deploy Relationship Graph metadata according to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_relationshipgraphdefinition.htm with Gearset. This metadata is required for the so called Actionable Relationship Center, which is part of Financial Services Cloud. Even though the meta data is available in the Vlocity filter in Gearset, the items we are looking for doesn't fall under that one. If selected, no meta data get retrieved and therefore no deployment happens.
6 votes -
Allow delegated users to edit environment variables
My user is setup on our CI and I have a number of environment variables setup on Custom Labels for ID's.
Whilst this works great the main issue is if I am Sick/On Holiday there is no way for someone else to go in and add/edit the environment variables thus making me a single point of failure/Reference.
What would be great would be either have Environment Variables setup at a CI level and delegated users have the ability to go in and edit/create new ones against the CI (This would ensure only those that know what they are doing are…
6 votes -
Ability to accept/disregard repo cleaner changes
I would like the repo cleaner to work more like the problem analyser, offering a chance to accept or disregard the suggestions before executing it.
Currently Repo Cleaner can only be enabled/disabled only at team level settings, thereby forcing the setting team-wide, which effectively rolls onto all the projects/repos using Gearset for deployments.
I have come across a situation where I would not like to alter the repo with changes any more than what I have actually changed, but since its a team-wide setting the repo cleaner was getting triggered in and bringing in more changes to my repo than…
6 votes -
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 -
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.
6 votes -
API to provision users, assign users to connected organisations
API to provision users, assign users to connected organisations
It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.
At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).
6 votes -
track metadata filter changes
Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.
6 votes -
Show Created By and Created Date when doing comparisons
When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well
6 votes -
automatic pipeline deployment on successful validation
For Pipeline jobs, provide an optional feature (ability to toggle on/off) where if an Open PR has successfully validated on the target org, then auto deploy to target org. This is useful when propagating changes in downstream jobs. For example, once code review is done, a PR is merged into DEV by pipeline admin, but it should also automatically be merged and deployed into QA if the validation is successful.
5 votes -
Automate Salesforce org connection on sandbox refresh
When we refresh our sandbox orgs, we have to reconnect the gearset user, would it be possible to use JWT to auto connect to the org?
5 votes -
Approval process for metadata deployment
It would be great to have a approval process for the deployment.
For example, once we have completed the comparison and validation, we can click a button "e.g.: Submit for Approval" and an email will be sent to a list of email.
In the email, receiver can review the summary of the deployment (e.g.: source org, target org, number of changed/new/deleted components, ...) and click on a link to approve or reject the deployment.
We can deploy only when the job is approved.5 votes -
Ability to recreate a reusable list or group for Deployment notifications
Every week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers.
It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already…
5 votes -
Change the Metadata Filters and make them first class
I would like to see a change to the metadata filtering in general.
Filter management has become a important part of our devops process as we seek to lower our comparison timing.
Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy5 votes -
Ability to select source target for Successful Deployment Notifications
Currently successful deployment notifications send every success to the specified addresses. Having the ability to specify the source would eliminate the unnecessary notifications to those addresses. We have a use case in which we only wish to send notifications for successful deployments to our production source.
5 votes
- Don't see your idea?