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.
262 results found
-
Please add support for decomposeCustomLabelsBeta
Salesforce added the option to configure multiple features in the DX Project Configuration file. One of the is breaking down the big CustomLabels file into individual files where we no longer need to deploy the whole file but just a file (label) that has changes in. Please see SFDX Documentation here - https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_config.htm
4 votes -
Offer Japan data residency
We are headquartered in Japan. Japan has data residency requirements for data backups/deployments and even metadata deployments/processing.
Please add the option for a Japan hosted Gearset account.
2 votes -
4 votes
-
Ability it use SOQL to provide complex filters on Vlocity and Salesforce Metadata types to create custom Compare & Deploy Filters
I would like to have the ability to enter SOQL queries to filter Metadata types and data. Currently you can only use Object or Regex when you try to filter the data to fine tune the comparison. We are looking to do this for Vlocity and Salesforce metadata types and objects
2 votes -
Allow Dev Updates to be Qued
Allow dev updates to be in a que so that you dont run into the problem of updating to many at the same time.
1 vote -
Update all Dev's button
Create a Update All Dev Sandbox button in a pipeline that allows you to quickly update all of the devs at once instead of clicking into each one.
1 vote -
documentation
I have been really impressed by the visualizations on the Compare and Deploy interface. Particularly the lightning page layouts and flows. One of my most time consuming tasks is creating internal documentation and I have not found a tool that allows me to capture the level of detail that I want in an efficient way. It would be great if I could export the visualizations at the bottom of the compare and deploy screen. It would be even better if it could export directly to Confluence.
1 vote -
Remove files from a PR
I want the ability in Gearset to selectively remove files from a branch or PR without running another comparison.
I have an admin that frequently "over commits" too many things.
Often its bad enough that its just easiest for them to delete the branch in github then start over in gearset.
The problem then is that starting over from scratch, a day or two since they worked on it, and they will make a different mistake.
I'm aware of a few features, like
Delete the branch in Github and start over in gearset
- Seems to be the easiest to me
…
13 votes -
Allow for different pull request messages.
I would like the ability to have different pull requests message per pull request that is autogenerated when you move through the pipeline.
Example: When I first create a pull request from dev to my next static environment the message would only pertain to that static environment. So from Dev to UAT I would include a pull request message pertaining to testing.
Then after that I would move from UAT to Staging so the message would be something about the testing and how it is complete and ready to move to staging which is our integration environment.
Then when that…
1 vote -
Update Slack notification messages format
Update the slack messages to more clearly define what happened in the action.
There should be a more clear title to the slack message. It should define what item was doing what. Currently that is grouped into a description which does not show on slack notifications.
CI job notifications should have a more clear "from where to where" section in the notification. Currently its grouped into the description.
1 vote -
All available branches display
Create a view that displays all active and available branches and there current commits and pull requests. That way if there a multiple branches per environment a release manager can see everything that is going on instead of having to click into each environment in the pipeline or going into git.
1 vote -
Show Auto resolved conflicts
When in the conflict resolution screen it would be nice to quickly see all files that have been auto resolved. Maybe with a icon of some sort on the left hand side next to the circle icon for resolved or not resolved.
1 vote -
Mass resolve auto resolved conflicts
Currently we have the auto resolve from previous environment feature which takes previous conflict resolution into account for a new conflict dectection run in a new environment. This is great but if I am deploying through a pipeline to multiple ORGs and the same conflicts that are auto resolved each time popup I need to keep clicking through them and marking as resolved.
I would like there to be a Mass resolve button that only resolves all the auto resolved conflicts. That way I dont have to click through each one even though everything is resolved already.
1 vote -
UI improvement suggestion
Hi, just a quick suggestion for improvement as someone who is using the Pipelines feature. Would really like to be able to get to the pipelines screen a lot easier - ideally with one click. Best case scenario is I can customize what I see in the left navigation panel and also choose to "pin" it. I've been a Gearset user for 7+ years and I still struggle to find what I need in that navigation panel. I think these features would make my life 10x easier!
1 vote -
Display auto-merged files during Conflict Resolution
The Conflict Resolution only displays files that require manual resolution. Sometimes I want to see the files that were automatically merged without human intervention.
The only way to see this is to submit a resolution as is, then read through the file changes again to look for files that were auto merged/resolved from target instead of source.
2 votes -
allow automatic publishing of an experience site after deployment
Just like you can automatically activate Flows in Gearset upon deployment; it would be nice to automatically publish deployments of Experience Bundles. This is especailly true for deploying Experience Bundles to staging/qa orgs but applies also to PROD.
There's an API to do this: /connect/communities/communityId/publish documented https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/connect_resources_communities_publish.htm
2 votes -
Visibility to Log Files for Connections and Compare & Deploy Events
When you either make connections to 3rd party applications or run a Compare & Deploy, there is no visibility to the log files, I feel these should be accessible to the user so that we can understand the reason why something is failing and not have to have someone provide this information. Additionally it should have options to change the level of logging to provide detailed information when needed
1 vote -
Implement a Ticketing Feature
Salesforce DevOps Center has a useful feature that allows users to create different Projects that have their own pipelines. Within each Project, you can create Work Items (similar to Issues in Jira). The user can then perform their work in a Salesforce environment and then run a comparison to associate certain changes to respective Work Items.
From there, each Work Item can be promoted through the various environments in the Project pipeline.
This is really helpful when working on numerous tickets/features for a given project, knowing exactly which environment each Work Item is in and the various metadata elements that…
3 votes -
Set up notification according to the target connection we're deploying to.
Set up notification according to the target connection we're deploying to. This way, the scheduled and manual deploys will notify us with what we set up.
1 vote -
Allow open PRs to queue up.
Allow open PRs to promote via selection and to queue up against the target keeping blocking behaviour to just merges and the deploy activity
1 vote
- Don't see your idea?