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.
324 results found
- 
New Feature: Filter Custom Fields (and other sub-components) in Comparison FiltersI'd like to be able to exclude certain custom fields from my comparison. For example we have fields that have environmental differences between orgs that we don't want to deploy. There are also random fields on standard objects that show up as "different" even though they aren't and it would be nice to filter them out. 4 votes
- 
I want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structureI want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structure for reporting. In this example the fact that "user A owns the connections and has delegated the permission to user B" is not visible to user C. Ideally user C would be able to see that delegation information for auditing purposes. 1 vote
- 
APEX Class ChangeAPEX Class Changes Reporting It would be really cool if, through the monitoring side, if a summary Excel could be created. Excel could have multiple tabs: 1 tab per class change with four columns: col1 :original line # 
 col2: original line value
 col3: new line #
 col4: new line valueHeader could include change DateTime, source/target orgs, Gearset ID, who, etc Thanks 
 Ron1 vote
- 
Allow users to create customized list views on the deployment history tabIt would be immensely helpful for our team, that works across dozens of production orgs and sandboxes, to be able to create deployment history filters (or list views like in Salesforce) that support filtering based on an org's mydomain, the username's domain, or the Gearset user that facilitated the deployment. 1 vote
- 
CI Job Email Notification with PR infoWe do receive an email notification when CI job is deployed. Is it possible to know which PR is deployed with that CI Job? Now, the email notification only has the info with branch name, source, target and deployment summary. it'll be great if we can know the PR name that is associated with this CI job, some users, like QA team, will receive emails and know the PR with card info is deployed so they are ready to test. thanks 1 vote
- 
Gearset Scratch Orgs: Generate PasswordsOur team would like an enhancement to how Gearset handles generating scratch orgs from authorized Dev Hubs. We want to be able to provide log-in credentials to non-gearset users in order for them to use these scratch orgs and perform development work. We want our deployment manager (gearset user) to manage the provisioning of scratch orgs and the retrieval of changes in these orgs to source control. Our developers currently just focus on developing features and are abstracted from the complexities of the deployment process. To make this process a lot simpler for our deployment managers, it would great to… 2 votes
- 
Add deployment job detail info (such as date/time) at the header in the detail viewI have a markup screenshot for the above feedback but I don't find a way to add attachment here. 1 vote
- 
Filter Deployment History by Source / DestinationAt this time, there does not appear to filter deployment history by specific orgs AND other criteria in the general "filter" text box. I would like to find specific packages deployed to a specific org and also that have a standard friendly name. I am only able to enter text to filter by the friendly name and the additional filters allow for source / destination type, but it does not allow for specific source / destination. 2 votes
- 
Add additional deployed packagesWhen combining packages for a deployment to a new source, it would be helpful if I could add additional packages to a comparison. There are times when I realize a package or two may have been missed in the original combination, and when reviewing the missing components, I realize a missed another deployed package. Without the ability to add additional packages to the comparison, I must start the combination of packages all over again. 1 vote
- 
Select All Option in Deployment historyIt would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target. 2 votesThis is now possible as long as a filter is applied to the deployment history page. 
- 
Ability to recreate a reusable list or group for Deployment notificationsEvery week we have a larger sized scheduled deployment for logic updates that runs after business hours. There's usually the same 2-6 people (often increasing) that want to receive an email and/or text message when the deployment succeeds. Whoever schedules the deployment has to add each one manually every time, and it would be nice to have a way to send notifications to a predefined list or group of email addresses and/or phone numbers. It usually has to be the person that schedules the deployment, because if someone goes back to add their own email or phone to an already… 5 votes
- 
When an Installed Package is installed via GS permission sets with View/Edit All Data system permission don't automatically get updatedWhen an Installed Package is installed via GS, permission sets with View/Edit All Data system permission don't automatically get updated for the new objects in the package like they do during a manual install. We then have to update the PS via deployment or manually or future deployments will fail with "Read All permission is required for [sObject]". I would think it would be fairly safe to allow GS to automatically add the appropriate object permissions to the perm set in the target org since Salesforce requires that all objects have, at minimum, the same level of access as the… 1 vote
- 
Export Validated PackagesAbility to Export Validated Packages from Grid, like Deployment History. 1 vote
- 
Ability for Enterprise User with Role "Owner" to Delete Validated Deployment by Other UserThis feature would allow Enterprise user with Role"Owner" to Delete Validated Deployment by Other Users. The reason for doing this is that there could be packages created in error and this would allow release managers who are typically owners to cleanup. 1 vote
- 
Add a deployed components count to the Deployment History tableWe'd like the ability to view the number of changes that were deployed from the Deployment History table view so that we can quickly scan the list of recent deployments and identify certain deployments using that additional information. 1 vote
- 
resize column widths on "deployment history" page (no truncated values)On the deployment history page, the column widths are fixed. If you have a value in the "friendly name" column that's over a certain character count, it gets truncated automatically. there is a tool tip to see the full value by hovering, but if you use consistent naming standards for naming deployment packages, this can result in having to hover over many package (i.e. rows) to find the one you want. if making the column width customizable isn't possible, then making the "friendly name" column character limit longer would be a good start! 3 votes
- 
Allow users to share deployment drafts across different Gearset environmentLets say multiple vendors are working on different environments and done the deployment across all the lower environments using their own Gearset. But coming to the production org. internal team will be performing the deployments using internal Gearset. So Instead of recreating the deployment draft again, it would be very useful internal team can reuse the draft created by vendor in different Gearset environment. 1 vote
- 
Change the Metadata Filters and make them first classI would like to see a change to the metadata filtering in general. 
 Filter management has become a important part of our devops process as we seek to lower our comparison timing.
 Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
 In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy6 votes
- 
Show data hosting option chosen for an accountIt would be great to see the chosen data hosting option for an account in the 'My Account' area. Without it security audits will not be able to verify what setting was chosen and will have to rely on documentation held elsewhere. 1 vote
- 
Delete comparisonsBe able to delete a comparison run with wrong filters or just keep the latest comparison 1 vote
- Don't see your idea?
 
          