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.
265 results found
-
Maintain version history for static code analysis rule set.
Need to maintain version history of static code analysis when creating a new set of rule ,who made the change , what was the previous version , what rules were there is previous version etc. Right now we cant even clone to create a new version and upgrade on top of it.
1 vote -
Gearset VS Code Extension
My development team spend their time in VS Code where they can see all their Git information etc. It would be great to have a Gearset plugin to stop them having to switch windows and allow them to have information at their fingertips. This could also encourage more developer use of Gearset.
May display:
- Build status
- Static code analysis issues
- View of pipeline1 vote -
Provide deployment options for Mulesoft via Gearset
As Gearset does Salesforce based deployments so well, it would be great to have Mule deployments done through Gearset as well.
2 votes -
Gearset CPQ deployment to delete target org component if source is deleted
Example in CPQ template you have situation when you need delete from source org component (content, line column etc.)
Now you have to delete this in target org as post deployment task.
Current solution support only new or changed component change.2 votes -
Download Package Option does not include custom fields.
Just wanted to flag that the Download package option would be so much handier if it also included custom fields. Even with custom fields selected in my comparison, the package.xml that I can export only includes the Objects.
1 vote -
Allow multiple connections to the same source control system
Currently you can setup as many salesforce orgs as you would like as a source/target but you do not allow the same with VCS/Source control systems.
For example, I can only tie a single account to a single bit bucket. What if you have muiltiple bitbucket accounts that have different accesses to different repos - there is now way to do this in gearset.
You should expand the source control systems to be just like the salesforce orgs - you can configure and share as many as you would like for the same or different systems.
1 vote -
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 -
Automatically Defer Sharing Calculations
Salesforce has a feature to "Defer Sharing Calculations" ( https://help.salesforce.com/s/articleView?id=sf.security_sharing_defer_sharing_calculations.htm&type=5 )
It would be awesome if Gearset Pipelines could have an option to utilize this, if sharing rules are included in Deployment, defer sharing rules for any validation / deployment, re-enable and recalculate after deployment
1 vote -
Include "Messages reported by Salesforce" during Metadata Deployment in the final report
During a metadata deployment, on the "deployment in progress" screen, there is a column for "message reported by salesforce".
I think these should be included in the final results screen, and perhaps in the deployment report.
These can be useful for the user to do things like make changes to their flows to conform to salesforce best practices.
2 votes -
Allow Jira Ticket Association Changes on Commits
Please allow the Jira Ticket Associated with a Commit to be updated once the Commit is Successful. If a mistake was made prior to commit and the incorrect ticket was entered, there is not currently a way to change/adjust the associated ticket to the correct one.
1 vote -
ORG Deployment notification
Set notification distribution at Org level besides users profile level.
People are interested on deployments to Production for example. But not everyone is as interested if a user deployed to another sandbox.1 vote -
Display Friendly Org name in deployment - validated and history
Allow to define columns displayed in deployment. I'd like to see Org Friendly name instead of username. We defined these org friendly names when the connection was defined. I'd like to see it as a column with the Deployment dashboards. Most often we care more of the friendly name than the username used to connect.
1 vote -
Write Deployment Results back to the user's Salesforce org
When setting up a deployment, it would be helpful to capture Deployment Results in a custom object in the running user's Salesforce org. Users would be able to specify a unique reference at the point of deployment, which would track through to the Salesforce org.
Information about the deployment would be captured in a Master record, with data about individual components existing in Detail records.
Org admins would then be free to leverage automation features to map the created records as they see fit.
As a consultancy that tracks our customer requirements in Salesforce, our use case would be that…
14 votes -
Ability to delete app visibility
As per the official reply from Gearset support
".....The issue is, if you manually delete the app, all the app visibilities will be deleted as well. But when using Gearset to delete the app visibilities, they are not completely deleted but set to false. The best workaround for this is to manually delete the xml from your git branch. ..."
If Gearset can incorporate this feature, it would be nice.
The workaround is not that hard as it may sound. 4 apps in 60 profiles takes about 10 mins to mass-find and mass-replace in VS Code.
1 vote -
Add configurable email reminders for scratch org expiration.
From Salesforce orgs and Dev Hubs, it would be great if there were a setting that would automatically send an email when a scratch org is approaching expiration. This could be configurable per Dev Hub, and would help prevent data loss at scratch org expiration.
1 vote -
Link to the Salesforce Validation in Progress from the Pipeline
When I deploy using the standard deploy interface, there is a link that allows me to view the deploy progress in Salesforce.
In pipelines, I would like this same feature. When a deploy has been running for a while, it's useful to know where it is in the process and a quick link would be quite nice.
2 votes -
link deployment to a salesforce case
The ability to link a Gearset deployment to a salesforce case record. If an org uses cases to track a bug or feature, this feature would close the loop from that case to the gearset deployment.
I understand that there is a post to chatter functionality but it would be nice to target a specific case for auditing purposes.
1 vote -
Provide and enforce branch naming conventions
Branches get all kinds of really stupid names over time. It would be nice if Gearset provided an option to template new branch names. For example when my users need to create a new feature branch for their user story, Gearset should prefix that branch with 'feature/'. When a release branch is created it should be prefixed as 'release/'. Bugfixes or Hotfixes could be bugfix/ or hotfix/.
Dictating naming conventions is unenforcable. Keeping branch names organized goes a long way to keeping the repository maintainable over long periods of time. Even if folks are well intentioned, git branches are case…
2 votes -
Yellow help icon
i love the help you guys provide, really great.
Suggestion.. The yellow circle that you open and drop down.
1) can you move it to the header, and if there is a pending message show the yellow circle with a number in it ( number is count of pending messages )
2) can you make it a separate window model? typically when i am chatting, i need to see the entire screen and the current pinned model is usually in the way and i need to click the arrow to get rid of it.
If i could drag the window…1 vote -
Ability to turn rules/processes off as needed with ability to rollback
There are times when need to update data or load data into Salesforce org and need to turn off rules or processes before updating data or loading the data. When doing a data deployment, GearSet has this ability, and I would like to have this ability to do this without a data deployment. Ability to turn off Validation Rules, Required Fields, Restricted Picklist, Workflow Rules, Flows/Process Builders, and Triggers one by one or turn off all. Then roll back once finished updates.
1 vote
- Don't see your idea?