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.
1308 results found
-
Add stacktrace column to Test Outcomes
There is no Stacktarce information on the Test Outcomes from the Unit Testing page. That information is important to help the developer team investigate the issues.
1 vote -
Audit history on Data Backup Jobs
For SOX compliance, we backup our Salesforce production data with Gearset. However, there is currently no way to determine the last time the job was modified. If at the bare minimum we had the last modified date & the user that modified the job, we would be able to confirm for the auditors that no changes have been made. Ideally, we would have tracking on the job for the different features - adding or removing objects, cadence of job, etc. For now, we're having to do a manual review.
1 vote -
Add testing steps to Jira ticket
Like the new feature for adding pre/post deployment steps, it would be good to be able to add testing steps to a feature in gearset.
1 vote -
I would love to be able to edit the name of a feature while it is in progress in the pipeline.
We include the release date as part of the feature title, but sometimes the release date changes after we create the feature and while the feature is still in the pipeline. It would be great if we could update the name of the feature at any point up until deployment to production.
1 vote -
Add Pre/Post Deployment steps for Data deployments
Some data deployments require manual steps pre and or post deployment.
Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,
1 vote -
Add Pre/Post Deployment steps for Data deployments
Some data deployments require manual steps pre and or post deployment.
Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,
1 vote -
Audit changes to the "Require issue tracking" setting
As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.
1 vote -
Fix comparison default date range
- Click new compare and deploy
- Select a source and target.
- Notice the date range says "Today" but DON'T change it.
- Click Compare
- Notice the date range now says "All Time"
Repeat...
1. Click new compare and deploy
2. Select a source and target.
3. Notice the date range says "Today"
4. Change the date range to anything else
5. Change the date range back to "Today"
6. Click Compare
7. Notice the date range now says "Today"1 vote -
Fix pre/post deployment steps from disappearing.
- Add Pre or Post deployment step
- Click "Specific environments only"
- Click the "x" to remove all the environments Notice, the entire "Environments to run against" section disappears To get it back you have to cancel, and do it again.
1 vote -
Add Omnistudio Features to Scratch Org Features list
When using the 'Create new scratch org' screen the following features are not available in the 'Scratch Org features' list
OmnistudioMetadata
OmnistudioRuntime
OmnistudioDesignerThese are available features according to the Salesforce documentation
1 vote -
Pull Request Changed Items View Fix
When viewing the items in a pull request in the 'Changes in this PR' section of the pipeline you only see the file name.
I would like to see something more similar to an actual comparison view where you have a tab with one column for the name and then another for metadata type.
Having just the full file name does not give me that instant information I need, especially when its a long file name and the type runs off the page never to be seen unless you hover over the file.
Converting to a table format might also…
1 vote -
Allow IN Operator for Data Deployments
When filtering for specific records with ID's, would be handy to have an IN operator for record selection.
1 vote -
Problem Analyzer while building the deployment
Surface problems with building the deployment to allow users the correct in the deployment.
1 vote -
Feature that allows users to post Deployment information to custom object in Salesforce
Gearset has feature to allow users to send depolyment information to Jira. Provide the ability to do the same to a custom object in Salesforce.
1 vote -
Please add 'Type' and 'Priority' field from Jira to Reporting API.
In the absence of 'Type' and 'Priority' field from Jira in Reporting API, it become significantly challenging to report on Cange Failure Rate and Mean Time To Resotre and rely on either on the Jira title or description, which is again a heavy lifting in order draw the report.
1 vote -
Add Salesforce Data Cloud sandboxes as an option for deployments
Salesforce Data Cloud sandboxes are now generally available but to promote changes from sandbox to production, the only options are through Data Kit and change sets, CLI, or DevOps Center. Having the option to use GearSet would be helpful so all deployments were managed the same.
3 votes -
Force API update for deployment
Please provide the ability to force API versions for deployments.
Allow the administrator to place an API version in a setting and when a deployment is validated or attempted deploy if the API version is the value or below then do not allow the validation or deployment.
1 vote -
Trigger CI Jobs on Gearset deployments
When setting up a CI Job originating from SFDC, we only have the option to trigger the job based on a time interval. Which makes sense since there are no events to subscribe to in SF for this.
But, I think it'd be helpful to be able to trigger a job to run on the completion of another Gearset deployment. This would be useful for automating the addition of metadata items like fields or layouts into source control, which are less-than-fun to create as xml files.
So rather than running such a job every 1hr, we'd ideally be able to…
1 vote -
Feature Request: API Endpoint & Webhook for Validation Errors
I hope you’re doing well.
I’d like to propose a feature enhancement for Gearset’s API that would greatly improve integration and visibility across systems like Slack, GitHub, and Jira.
Feature Request:
• API Endpoint:
Expose the existing endpoint as part of the Gearset API: https://us.app.gearset.com/api/validation/started/{jobId}/result that returns specific error messages for failed components after a validation attempt.
This would allow us to programmatically retrieve validation outcomes and integrate them into other systems for better tracking and visibility.Webhook Support (Bonus Feature):
Even better, adding webhook functionality to push validation results directly to external systems (e.g., Slack) would streamline our workflow.…1 vote -
enable using a Repository Access Token instead of a Service Account
I would like to be able to use a repository access token instead of a service account to connect to VC (Bitbucket in my case). https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/
The main benefit for me would be the ability to conveniently authenticate while maintaining a high level of security, even in situations where corporate change management policies and SSO requirements can be cumbersome.
3 votes
- Don't see your idea?