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.
1286 results found
-
Consolidated Reporting for CI Jobs
Hello. One item we struggle with is keeping track of CI Deployments that didn't fail, but didn't deploy as expected. The two causes we usually see are:
1) Something was removed by problem analyzer
2) We deployed something that Salesforce says succeeded, but no changes were made (e.g. deletion of picklist choices)We currently have about 100 CI jobs which makes it impractical to go into each one.
The proposed format would look like a csv export:
Job Name, Date, # Created, # Updated, # Deleted, # fixed by problem analyzer
Opening a CI job history looks fine, but we'd…
1 vote -
Provide More Detailed Information on Data Deployment Summary Steps
Currently the data deployment summary displays an elaborate interface but with very little useful information other than record counts. On the right side are Steps, but those steps do not tell the user much. I can see that in one step x records were fetched, for example, and in another step y records were fetched, but I can't see WHY.
Example use case: I had a situation where I was filtering an object but the filter wasn't being honored (more records were being deployed than expected). I could see from the data deployment summary that one of the steps was…
1 vote -
Add a way so we can easily integrate commits into Salesforce.
What I mean by this is, give users the ability to create and associate commits from in Gearset to a custom Object in Salesforce.
The commit would create a new record in Salesforce, under the custom object, let's call it 'Commits'.
We'd be able to pass through data such as the commit status, the ID of the commit, a link to the commit itself taking us back to Gearset, the name, and author, etc, etc...
I'd imagine this is possible through the use of the BitBucket API, however with SF teams who lack developer resources, this would be a nice…
1 vote -
Allow Filters to be Customised in Pipelines UI
Currently, you can create new filters in Compare & Deploy, but when you are comparing and deploying from within the Pipelines UI on your development org, you can only select existing ones. This either means you have to get your team to go into standard Compare & Deploy to set up specific filters first, or they always have to select the filter that includes everything.
1 vote -
Change language to focus less on Source Controls and be more user friendly
Gearset is great for non-technical users or those that find Source Control daunting. However, the terminology used in Source Control has leaked over to Gearset, and I think this detracts from the useful aspects of it, and at times just makes it feel like an extension of Source Control.
e.g. "Create Pull Request" in the Pipeline UI should be labelled something more friendly like "Request Feature Deployment"1 vote -
Hide the "Create Pull Request" button on Deployment Success Screen
Currently, we are setting our team up to use Pipelines, which has the benefit of guiding users down the pipeline in the right way (they can't create a pull request from a qa branch straight to main without going to uat for example). However, when they perform a commit from an org to a feature branch, the Deployment Success (commit success) screen has a button that allows them to create a Pull Request directly to any branch that they want. There should be an option to hide this from users, especially given the benefit of only being able to move…
1 vote -
allow field level granularity in CI Jobs
Would like the possibly to set up a CI job that only syncs a sub-set of fields on a custom object. For example, we have an org to org sync where we want to update picklist fields but not autonumber fields. Currently we are running this job manually twice a day.
1 vote -
Enable admin visibility into a Gearset team member's shared orgs
As a Salesforce implementation partner (SI) I have a lot of organizations to manage, well over 50. Each time a new org is added, I can go through and add all the users to that org, but whenever a new person is added to my team, I have to go through each connection and add that user to the list.
As the owner, I would also like to be able to see all the shared orgs inside my account, so I can centrally manage them, rather than just the ones that team members may have added.
1 vote -
Prevent deployed validated packages from being deployed subsequent times
Currently, after you deploy a validated package it no longer appears under the Validated Packages menu, however, if you still have the link for the validated package and navigate to that package it doesn't give you any indication that the package has already been deployed and allows the user to click the Deploy button again, assuming they have deploy permissions on the target org connection.
As part of our production deployment approval process, we store the link to the validated package in our external ticketing system (https://app.gearset.com/validated-package-details?deployPackageId=<package id here>). When completing the ticket, users use that link to…
1 vote -
Allow more than one instance of Jira to be connected to.
It would be great to have the capability to connect to more than one instance of Jira. We are switching to a different instance and we have to delete and recreated the Jira connections each time we switch instances.
1 vote -
Allow account admins to run reports on their team's usage of Gearset.
I am managing a Gearset account and I need to be able to know who is using Gearset and who isn't so I can more properly assign licenses.
This might be an Enterprise feature, https://app.gearset.com/account/account-report, but really should just be something an account admin can run.
1 vote -
Pull Request From Deployment History
Making a pull request via Gearset is only available from the Compare & Deploy Flow.
I'd the link to make a pull request available from deployment history so that users can make the pull request to the various Git/Salesforce environments.
Currently, I am telling my users to note the deployment id for their comparison and hit the link. This appears to work, but isn't user friendly.
https://app.gearset.com/finished?deploymentId={deploymentId}¬ify=true
1 vote -
Show me where the Salesforce Release Changes are in the metadata files.
As a gearset user, I want a guide to the location of metadata components created by Salesforce in each new release so that I don't have to guess and look for the metadata 3 times per year when Salesforce publishes changes to their platform.
Please user your business relationships with product owners at Salesforce to submit this story idea on behalf of clients everywhere.
For example, today I was looking for metadata, if any, created by enabling permission set expiration dates in my sandbox. This won't be availabe in production until release on 10/7 but I was curious if I…1 vote -
enable UTAM
In the same way you enable Jest tests to run during deployment like that:
https://docs.gearset.com/en/articles/5204895-pilot-feature-source-control-setup-for-lwc-test-runs
We would need to run UTAM tests:
https://utam.dev/guide/introductionThose are stored in utam folder and as sucha re not deployed to Salesforce org but rather "ran" by the test system.
UTAM is very similar to Jest but do a simulated browser test (including integrated services and login of users) that covers full scenario and several pages. It's possible by using Chromedriver through WebdriverIO. All these are nodejs libraries used by UTAM.1 vote -
Add feature for admin to disable all email notifications globally from the profile
Add feature for admin to disable all email notifications globally from the profile
1 vote -
Show expired orgs in list of salesforce orgs
When checking my list of salesforce orgs it would be good to see that the listed orgs have valid tokens and if they don't have valid tokens either checked on the fly/daily etc or just from previous automation attemps/backup attempts this would really help when you have access to many sandbox orgs on your user account.
https://i.imgur.com/j0qb4Bq.png Example possible implementation?1 vote -
Include Apex classes regardless of folder
In GitHub, Apex classes don't always have to be in a folder called "classes " to work with them. Some people using SFDX put test classes in their own folder (sometimes called "tests". Even Apex classes within the "classes" folder can be sub-grouped into folders. (Example at https://github.com/trailheadapps/apex-recipes/tree/main/force-app/main/default/classes)
I'd like Gearset to scan the entire repository and to group metadata by its actual type, not by the folder it is in.
I'm not talking about the sfdx-project.json saying where the metadata is located. This is within each of those locations, it should find all Apex (for example). The Apex…1 vote -
Support Filter by Status from Monitoring History
I occasionally need to review the Monitoring History for a particular org over a period of more than a few days (eg. Last 30 Days or more). I'm only interested in reviewing entries where the Status = "Different" so I can quickly ignore those that are "Identical". This would be a good place for a column filter like those that you support on the Compare & Deploy page.
It would also be nice to have the ability to filter on other columns (eg. Changed, New, Deleted, etc.) like only those entries where New components were added.
Thanks in advance!
1 vote -
Page layout comparison in Same Org
It would be so valuable and help immensely with tech debt to be able to compare page layouts and lightning page layouts within an org to see what the differences are.
1 vote -
dynamic search function after comparison
dynamic search function
it would be helpful after the comparison to look for multiple components at the same time and not each one individually. for the release we get a list of components example from the developer:
CustomerAddress
CustomerNamec
Customer_Telc
...I want to include the entire list in one search, and I want gerset to search for each row individually. Example in SQL:
SELECT * FROM table
WHERE column1 LIKE '%customeraddress%'
OR column1 LIKE '%customernamec%'
OR column1 LIKE '%customer_telec%'
OR column1 LIKE '%customertele_c%'
...this change would save us…
1 vote
- Don't see your idea?