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.
1430 results found
-
Compare org monitoring from an arbitrary date to the current state of the org
In Monitor ORG's tab, we have a daily set of cached metadata that can be used to troubleshoot issues in an ORG. This is great that we have this data. What would be even better (if there is not a way to do it currently), is if we could take the metadata cache from the monitoring job, "x" days ago, and compare it to the current state of an ORG.
Maybe an ideal way to achieve this would be to select a cached version in the Compare Organizations screen. Alternatively, a button can be added in the Monitoring Job history…
3 votes -
A count of differences could be grouped by type
If the count of differences could be grouped by type/color that would be helpful.
Ex: 20 differences: 5 red, 7 green, 8 yellow. It gives a better sense of how drastic the differences between Source and Target are at first glance.3 votes -
3 votes
-
Allow deploying fixes / linking work to closed Jira tickets without reopening them
Currently, deploying a fix related to a closed ticket requires reopening it, which triggers unnecessary notifications to the reporter.
It would be helpful to allow linking or deploying fixes to closed tickets without changing their status, or alternatively make it easier to search and reference closed tickets.2 votes -
Notifications/Reminders for Promotion Pre/Post-Deployment Steps
When a deployment is waiting on a pre or post deploy step, send a Slack notification or email. These are easy to forget about (or they are completed, but the dev forgets to check them off). Even better would be if the Slack message tagged or emailed the user it was waiting on.
2 votes -
Conflict Resolution Comments
It would be great if there were a way to leave notes or comments for each specific action I take or selection I make during conflict resolution in Gearset Pipelines. This would really help other people understand the reasoning and history behind conflict resolution activity for future reference.
2 votes -
Suggestion for Org Intelligence Enhancement
Add a dashboard within Org Intelligence that tracks metadata changes. Provide the ability to select a date range and view changes across key metadata types such as Objects, Fields, Validation Rules, Apex, Page Layouts, and more.
The dashboard should include interactive filtering functionality that allows users to drill down into individual metadata components. It should also allow customization of which metadata types are included and display rollups summarizing changes, deletions, and modifications, along with details on who made each change.
2 votes -
Add originating Sandbox(es) as a PR comment
It would be awesome to be able to see what Sandbox/org each commit (and thus PR) originated from. There is not many places to add the information to VCS as you can add comments only in the PR stage, but could you for example add comment to PR when promoting with the list of all commits + their origins?
2 votes -
Add support for Jira Service Accounts
Jira has (finally) added Service Accounts, so that full Jira users are no longer required. Would be great to take advantage of this. For reference: https://support.atlassian.com/user-management/docs/understand-service-accounts/
2 votes -
Add Webhook Error Logging and History for Outgoing Webhooks
When configuring outgoing webhooks (e.g., to GitHub Actions or Slack), errors and failures are not surfaced to the user, making troubleshooting difficult and time-consuming. Currently, after a webhook is triggered (or fails to trigger), there is very limited visibility into what payload was sent, what response was received, or whether an error occurred. If a webhook fails silently or returns an error, I have no way to view detailed logs or the history of webhook attempts. Furthermore, error messages (if any) seem to clear out whenever CI job settings are saved, and there is no persistent record of webhook activity.…
2 votes -
Add the ability to track who configuration changes to pipeline, CI jobs, etc...
It would be nice to see when there's a configuration was changed such as required test configuration on a CI job or pipeline configurations.
2 votes -
Mobile Support
Support mobile devices.
The CSS Used for the Pipeline Environment popover prevents the browser from scrolling horizontally. You can try this be logging into Gearset on your phone's browser or by narrowing the browser width on your desktop.
- I want to deploy from my phone.
- I want to monitor PRs from my phone.
- I want to browse my Scheduled Jobs and Monitoring Jobs.
2 votes -
Allow backup job permissions to be control by Roles
Backup permissions are separate from the Roles, causing duplicate permission maintenance. Please allow backups to use Roles instead
2 votes -
add support for lightning types (LightningTypeBundle)
Add support for lightning types (LightningTypeBundle)
2 votes -
allow us to automate the PR Syncs after a shedule deployment occurs
due to drift occurring because of the environments being out of sync after a deployment occurs I would love the capability to scheduel an automated PR sync after a successful scheduled release deployment occurs. like a checkmark box on a per sscheduled deployment basis.
2 votes -
Enable Excel export of org differences—profiles, permission sets, and objects—in the same side-by-side format with change indicators
I compared two profiles from different orgs—specifically, the old and new environments of the same company—to identify any differences and present them to the client for review and approval of necessary changes in the new org. However, I was unable to export the comparison results into Excel. It would be extremely helpful to have the ability to export the comparison data in the same structured and visual format as shown in the Gearset comparison window, making it easier to review and share with stakeholders.
2 votes -
Make components searchable across features in the pipeline
If I know the name of a component, Can you give me a way of searching through the pipeline to see what features it resides in, where they are and when it was deployed please
2 votes -
Automate upstream branch syncing
After merging/deploying to prod allow auto-creation of sync PR's to upstream branches/orgs (QA, UAT, Staging, etc...). If the sync PR's could be promoted automatically that would be amazing.
2 votes -
Delete Flow by Version Number
It would be beneficial to delete specific inactive flow versions. Examples where this would help streamline deployment changes:
You need to delete a custom field that is used in a flow. You create a new version of a flow, remove the dependency on the custom field and activate the new flow. Now you want to remove the flow version that still has the custom field dependency. Something like a checkbox to select the version(s) to remove.
You have inactive versions of a flow and you want to clean up the historic flow versions. Something like a checkbox to select the…
2 votes -
Add folders to Data Deployments for better organization
To help with organizing data deployment templates it would be great to have some sort of folder structure to allow us to group data deployments by team. We have several Salesforce Teams at my company and we all have slightly different data deployment needs. It would be great to have team folders for data deployment templates...for example Sales Team Templates, Service Team Templates, Marketing Team Templates, etc. Today we use some naming conventions which is fine, but would be a little cleaner if we had a folder structure. Thanks for your consideration.
2 votes
- Don't see your idea?