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.
1289 results found
-
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 -
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 -
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 -
Help to have a change log, including the name and email of the person who changed the test level in CI jobs?
The test class level change in the job is crucial for us; if someone changes the test level to no test in place of a specific test run, components will go without a test run.
So, if we monitor things on a regular basis, we can ensure that everything is in place.
If we have a tab to get all these kinds of information, such as reports1 vote -
Gitlab Self Managed Issues
We suspect that reading the 'weburl' response field for the specified branch from an API call to GET 'v4/projects/$projectid/repository/branches' might be causing a problem when using public Gitlab proxies.
We suggest implementing a code change to compare the domain of 'web_url' to the self-hosted GitLab domain provided by the customers. The customer's self-hosted GitLab domain should take precedence.
1 vote -
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 -
Soft delete User accounts
If you ever delete a user then that account can never be used again or added back. Rather than provide a warning with text that not everyone is going to read it would make more sense to not even have the delete option in the first place or do a soft delete where it can be reactivated. We have employees that have left the company and returned so its not an uncommon scenario. If someone leaves or an account gets deletes accidentally it would be nice to have some sort of recovery option then to not allow that email address…
2 votes -
Please adjust problem analyser feature to show record type changes when a picklist field value is added.
Currently Problem analyser does not show any warnings or issues when record types are not selected for a picklist field changes( value addition). With this during deployment there is fair amount of chance that some one could easily miss record type changes. Please adjust problem analyser to account this situation and show record type changes as warnings would be beneficial.
2 votes -
Allow deployment of 'Check For Matching Records' in Flows.
As part of the new Salesforce Summer ’24 release, Salesforce have added the ability to check for matching records when using a ‘Create Records’ element. We’ve used this useful feature in various locations within our new flows to identify existing contacts for example.
When deploying the flows using this feature between developer environments via Pipelines or Compare & Deploy in Gearset, we’ve noticed that this new setting within the element doesn’t get deployed and is switched off in the destination org.
In the meantime, we can manually turn on this feature in the destination org.
1 vote -
Save sort order in Saved comparison pairs
It would be nice that the chosen sort order of the saved comparison pairs could be saved.
If I choose to sort the saved comparison pairs on Friendly name and i open a new tab of gearset, the saved comparison pairs in the new tab are sorted on last used. It would be nice that in the new tab, the saved comparison pairs are sorted based on the same column as the previous tab.1 vote
- Don't see your idea?