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.
224 results found
-
Enable a consistent, buildable set of Metadata for Releases
I'd like to have a way to work with a consistent set of metadata items for a release, that I can add, remove etc, and consistently deploy into a variety of sandboxes and ultimately Production.
Currently, if you clone a previous deploy, items are de-selected if they're the same between the environments being compared. That means once I've deployed, I can’t ever get that “list” of items back and I have to rebuild it every time.
A likely scenario is that I've deployed some metadata from Sandbox A -> B. Lets say it's 5 Apex classes. I then realize that…
1 vote -
language
Gearset UI Language specification. Allow users to specify which language they want the UI presented in and then show the correctly translated terms in that language. When using google to translate the UI the words it chooses are not always relevant.
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 -
support blank values and/or regex in the "Find What" field on Environment Variables
...support blank values and/or regex in the "Find What" field on Environment Variables.
I would like to replace the value in a field on a Custom Metadata Type with an environment specific value, regardless as to what the value is in the source file. Currently I need to specify an specific value in the source to be replaced.
3 votes -
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 -
Send Email when a package is Validated successfully with PDF of Deployment Summary.
We currently receive an email with deployment summary as PDF attachment after successful deployment, but we also want this feature for successful manual validation. This is help us review the validated package summary with Deployment approval teams in our ORG.
2 votes -
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 -
Only notify the Pull-request creator on validation errors
Hi team, not sure if there is a way to do that in the current setup, but I think it would be helpful to add the option to only notify the Pull-request creator/owner on the validation errors, instead of "hardcoding" the email recipients. Regards, Adrian
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 -
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 -
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 -
Add schedule deployment for Pipelines
It would be great to add a new feature to cherry pick and schedule deployment for the changes that have reached up till staging/uat and should be released to Prod. Without this feature it becomes difficult to manage releases to avoid downtime.
4 votes -
Setup using Github Enterprise edition although behind a Proxy
I am running a Github Enterprise edition, but have to configure using custom git setup.
Using the Github Enterprise connection setup, I was able to connect; however cloning the repository failed as the http request to list repositories returns the private host name instead of the proxied one.
Clone functionality works when using the Custom Git link; however it limits our ability to make pull requests and it also requires entry of Username and Password instead of OAuth which is a security concern.
Create a feature which allows the hostname initially entered in Enterprise Setup to be used in favor…
2 votes -
Retrieve Metadata into local environment (e.g. using VSCode pluging)
This would make the integration of Version Control and Gearset nicer. Where now user has to go to Gearset deploy to a feature branch, afterwards, go to VSCode pull from the feature branch.
1 vote -
Rolling back deployment made by CI JOB
Currently it is possible to roll back a deployment made by CI Job, though that rollback will only be performed to the specified Org. Hence, other Orgs have to be rolled back individually.
Use case: I have propagated changed from my Sandbox to Staging. An issue was identified that requires a substantial amount of work where that feature cannot be included in the next deployment to production, hence it needs to be removed from Staging. Though, other sandboxes back propagated that feature because they assumed it should work.
It would be amazing if the rollback used Github commits, so the…
1 vote
- Don't see your idea?