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.
337 results found
-
Upgrade to PMD 6
PMD 6 includes useful stuff like allowing annotations in the code to suppress warnings. It would be great to be on that version.
Stephen told me via the support chat that it wasn't simple to just upgrade, so I thought I would submit it as a feature request.
2 votesHi Aidan,
We’ve now upgraded to PMD 6.3 which includes support for suppressing warnings.
Regards,
Stephen
-
Allow default repo to be set in Manage Connections and use in Comparison
This does not appear to work.
- Setup connection to source control GitHub that your user credentials includes multiple repos (in my use case, there are about 100)
- Do a Comparison, in the target list of repos, you will see all 100
- Select your repo (say repo #77). Do the Comparison
- Logout
- Login. Repeat step 2.
RESULT: repo#77 is not defaulted. You have to reselect it.
Either fix the aforementioned issue so the repo you most recently used is 'sticky' or allow specification of a default repo on the Connections page for each repository type.
1 vote -
Allow multiple ownership in Gearset
Currently only the creator (owner) of Schedule Test, Monitor Orgs and Manage Orgs can edit these activities. It would be helpful if we could designate more than 1 Owner for these activities. Similar to granting access to the various orgs (Comparison, Validation& Deployment) it makes sense to also include an Owner access as well.
If this is not possible, having a transfer ownership button would be helpful for each activity.
Thanks!
16 votes -
Sort order of Orgs ignores friendly name
If you have friendly names for your org connections, the list of orgs presented on the Comparison page ignores these and instead sorts on sandbox name. Since the lines show friendly name left most; this is not natural to the human to see things out of order
Example
OrderFix (joe.blow@foo.com.story003)
Invoicing (joe.blow@foo.com.story010)
AlphaTest (joe.blow@foo.com.story091)when what the eye wants to see is:
AlphaTest (joe.blow@foo.com.story091)
Invoicing (joe.blow@foo.com.story010)
OrderFix (joe.blow@foo.com.story003)1 vote -
Support more than one Dev Hub (sfdx) per Gearset Account | Manage Orgs
The Manage Orgs tabs only allows one to have at most one Dev Hub. This can be limiting in the following use cases:
Your Gearset user account is associated to a PROD org that has Dev Hub enabled yet the Gearset user wants to experiment with sfdx and Gearset using the SFDC Trailhead-recommended 30 day Dev Hub Trial Org
You are a consultant working with multiple clients, each using SFDX and hence each with their own Dev Hub. Yet as consultant, you have only a single Gearset account.
3 votes -
Active Link to Deployment Destination
When you finish a deployment you get a "Deployment Summary" screen that has handy details. It does not, however, have a link to the commit/branch in Github or other site where the destination ended up. I have to jump to my Github page and refresh instead of having a direct link. Yes, it's a tiny feature but is useful for a Gearset newbie like me.
1 vote -
Display API version underneath source and target on Comparison In Progress and other pages
When deploying from org to GIT or vice-versa, the API version being used should be echoed (small font) everywhere the source and target names are shown (such as at top of Comparison in Progress)
This is especially important for GIT where Gearset in the absence of other info will default to V37 that in turn causes issues with picklist comparisons. It can also be important during Sandbox Preview of new releases
1 voteWe’ve now shown this on the `In Progress` page.
If there are other places you’d like to see it, then feedback always welcome to submit an idea for that specific page!
Kevin
-
bug -- Refresh comparison with a selected item that on the refresh is no longer changed
If you have a piece of metadata that was changed on a comparison then a subsequent comparison using the 'Refresh Comparison' button. The selected item is still selected and unable to be deselected.
1 vote -
Rollback deployments made by CI jobs
Manual deployments and change monitoring jobs can be rolled back. Add the same function to CI jobs in case it accidentally deploys something unwanted
27 votesWork completed on December 22nd, 2021
-
Combine multiple deploy packages into one
It would be nice to have the ability to select multiple packages in the deployment history, and clone all of them into one comprehensive deployment. This would help when there are multiple features moved at different times to a QA environment, but would like to move them all at once to Production.
28 votes -
Add org name column to deployment history
We currently have to prefix the deployment friendly name in deployment history with our sandbox/org name to be able to sort by target. It is not easily filtered either as the name column includes both source and target. We would like to have the target org as its own column in deployment history, and have it use the org friendly name as the value if one has been set.
6 votes -
Static code analysis - allow for exclude patterns on classes
The new static code analysis feature using PMD is a good first start but there are too many false positives to make this useful
Here is one place to start:
Allow for specification of regex patterns to exclude classes. Specifically, classes that start with xxxx_ would be most helpful as it would allow us to remove from analysis unmanaged packed code like fflib (Enterprise Patterns) or sfab (SobjectFabricator). There are hundreds of lines of PMD rule alerts from these classes
1 voteTeam owners can specify exclude patterns on the rule set configuration page.
-
When deploying just a Visualforce page, don't automatically run Apex tests
When deploying just a Visualforce page via a Salesforce change set, the default option is to not run Apex tests. Gearset should mimic that default behavior.
2 votesThanks for the feedback Rob, this is now live in the app and we’ll default to the standard Salesforce behaviour
-
Be able to require a commit message for deployments
Sometimes a user may forget to add in a commit message before deploying, so the history in our source control is "no commit message" which is not editable. Can we add a feature to be able to turn on marking commit messages as a requirement for deploy?
10 votesThis has now been shipped.
The team owner can now enable deployment notes to be required via the setting located in the account summary page.
-
Allow scheduled jobs to be assigned a different authentication user
We would like the ability to change over scheduled monitoring/testing jobs to a different authentication user. Currently if we need to switch an authentication we lose the history.
Consider:
I leave my employer and I need to switch the monitoring over to another developer or admin. I have to delete all the current scheduled jobs and re-create them using the other users authorization. Which causes the history to be lost.11 votesThe feature was completed. The documentation is at https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Search for test classes
It would be nice to be able to search for test classes instead of having to type them out in a comma separated list. Gearset already has such a nice search capability and it would be great if it were applied to that dialog as well.
8 votesWe have made a release to address this, can you please let us know if this matches your expectations?
-
Live chat button overlays action button
Not sure how you resolve this one without moving either button. Maybe do something similar to what is done in the Diff view (where the action buttons are displayed in a row below the content).
Another option would be to have the live chat in the header navigation to toggle the feature on / off?
Not sure...Just noticed that it gets in the way sometimes.
4 votesWe’ve now made sure that the Live Chat button doesn’t appear on top of any of our action buttons.
Let us know if you see this one creep back in!
-
Ability to compare and migrate object data between Salesforce orgs
The metadata compare and deploy is outstanding and works well. What would save configuration and release engineers even more time would be an object data compare / sync. Sometimes, salesforce releases may only require a data migration. Hopefully, this feature will get a few upvotes from the community as well.
14 votesThis has now launched as part of our data deployment feature.
https://gearset.com/product/data-deploy
This is an opt-in feature, that doesn’t change the default security profile of Gearset for those users that choose to use metadata only
-
Add a Save As to Save Draft Deployment
Add a Save As or an alternative way to create multiple packages from the same comparison. I have an existing comparison run and I want to stage the deployments, deploying some today and the rest next week. It would be more efficient to save both packages now as I am going through them, saving one for example as Dep120916.1 with half of my selected object and another one called Dep120916.2 with the remaining objects to be deployed later.
13 votesFrom the results page, you can now select the Save as option from the button toggle menu.
-
Can't navigate away from Validation in Progress
When I have a deployment or validation in progress, I can click on the main navigation but the page doesn't actually navigate to the target page.
The URL will change in the address bar, but other than that, nothing happens. If we shouldn't be navigating away from the validation progress page during a validation, please include a message in the UI explaining as much and disable the navigation (or have it open in a new window / tab).1 vote
- Don't see your idea?