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.
1309 results found
-
Permission set changes not displaying without drilling down
You shouldn't have to drill in to see the changes in a permission set. I was stumped b/c it showed no difference, but in reality I had to drill down to see the difference. This is bad UI
9 votes -
Increase API call limits
There currently is a API limit of only 10 calls per hour for the reporting and audit API's. This makes it difficult when developing and testing applications that tie into the api. In our case we use the api to pipe the data into our observability platform for reporting and dashboarding. It would be nice to either increase to something not THAT low or to have a development override option of some sort that customers to request to temporary increase. I understand the need for some limits due to having a shared cloud platform but this seems to be on…
3 votes -
Grouping developer sandboxes in Pipelines - back-promotion to a group
Team,
Currently Gearset Pipelines only offers the option to connect a developer sandbox group to a single downstream environment. While back-promotion to a group isn't available yetCould you please enable it ?
3 votes -
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…
4 votes -
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 users to select a default comparison view between 'Permissions View' and 'XML view'.
During comparisons, I constantly have to select the XML view when I click through rows of metadata as it keeps defaulting back to the Permissions View, I don't particularly find the permissions view that useful and I'm also used to XML views, would appreciate if you could give users a choice in a 'default' view to improve experience.
2 votes -
Unsubscribe from commit emails
Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).
1 vote -
Automatic analysis for metadata
Adopt automatic validation for API names of custom objects, custom fields, custom settings, and custom metadata types. Additionally, ensure that the "Description" field is populated to enforce documentation by administrators and developers on Salesforce metadata, including custom fields, custom objects, automation (Approval Processes, Flows, Entitlement Processes), and other applicable metadata types.
2 votes -
new comparison tool issues
new comparison method/view has a few bugs/bad ideas
when selecting a comparison pair & comparison filter on the "saved comparison pairs" page, the chosen filter does not carry through to the new screen & has to be re-applied
once in the comparison screen, there is no "sele3cted" button like on the legacy page. - this is crucial to know where I'm up to with selecting the parts to release.
2 votes -
Improve visualization of multiple features being simultaneously worked on in a single developer sandbox.
Currently, one must select (or create) a single feature+branch in the developer sandbox. The pipeline view only shows 1 active feature at a time. It would be nice visually see all of the features an individual developer is working on/assigned to.
1 vote -
Gearset Pipelines Sandbox Environment
In order to test new Jira webhooks, GitHub actions, and any other release management changes,
We would like a Gearset sandbox environment where we could test release management changes like new/updates to Jira webhooks, GitHub actions, and other related changes.
1 vote -
Display pipeline webhook errors in Pull Request details
Scenario:
- Feature branch created, commits added, Pull Request opened and pushed part-way through the pipeline.
- Pull Request has merge conflicts on one of the environments. Conflicts are addressed, but (let's say) PR fails validation so it is not promoted.
- New commit is added to the feature branch.This commit will generally fail to propagate into the above mentioned PR branch (triggering a webhook error). It would be GREAT if that error were somehow displayed on the PR details screen.
1 vote -
Add support for CMS Collections
Please add support for CMS Collections in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Collections in our current developments of a customer community and we'd like to deploy this metadata as well.1 vote -
Automate Jira Status when a Pull Request is created in Pipelines
Presently, the capability to automatically update the Jira Status of a ticket is limited to transitions occurring between different environments in Pipelines. Enhancing this functionality to include automated updates triggered by the creation of a Pull Request would prove beneficial, eliminating the need for manual intervention when transitioning to stages such as "Code Review."
6 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 -
Vlocity Metadata Types collapse during Compare & Deploy
When you start the Compare & Deploy, for Salesforce Objects, you see all the metadata types broken out as they get completed for 204 types. For Vlocity there are 83 types to select, but when you run the comparison, it collapses to just 1 type of Vlocity. It should show progress similar to hwo the Salesforce Metadata types work
1 vote -
Customizable Messages for Jira Ticket Associations
When a Jira ticket gets a new comment from a validation or deployment, it's a pretty standard message:
Deployment succeeded: link...etc.
Deployment Notes:
Source: ----
Target: ----
And then a table of differences that were pushed through.My thing is, none of this is customizable, whereas I'd love to be able to potentially change what's automatically appended to our tickets to make it more user-friendly for the reporters on those tickets.
1 vote -
Notifications for the errors in the webhook page on Pipelines page
Add possible to configure notifications for the errors in the webhook in the Pipeline. Similar to CI Job notification. Ideally post to Slack
1 vote -
Query for Deleted Records
It would be helpful to have a way to query for all deleted records across multiple backup jobs for a specific object.
1 vote -
Allow tests to be run in parellel in multi orgs and allow aggregations of results for PR validation and speed up non prod deployments
We get 100 sandboxes, Can create test orgs org1, org2, org3 where our unit tests are split and run in them so hour long tests just take 1/3 the time? We would like it to be part of our pipelines as of now PR validation to develop takes 40 mins which makes it unustainable.
1 vote
- Don't see your idea?