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.
357 results found
-
Functionality to Data Deploy Active Orders
Salesforce doesn't support the creation or update or standard Order records with a Status Category of Active. This means Gearset is unable to data deploy any active orders. It would be very useful if there was an option for Gearset to temporarily set active orders to a draft status for the deployment or the Order Records and related Order Records, and then set the status back to Active for the final step.
4 votesYou are now able to dow this with Gearset Data deploys
-
Add friendly Name to Deployment detail and be able to add/edit from that page
It'd be great to see the "Friendly Name" in the Deployment Summary page.
e.g. https://app.gearset.com/finished?deploymentId=XXXXXXXXX
And to be able to add/edit the Friendly Name on that page, same as it can be done in the Deployment Summary.
Our use case: We audit all our deployments to make sure they have a name. It would be very helpful to be able to send a Deployment Summary link to a user to tell him to add a name if it's missing.
5 votes -
Ability to create Pull Requests for AWS CodeCommit
Gearset can create Pull Requests for many of the source control systems that it integrates with, but not AWS CodeCommit.
As AWS users, it would be very useful to use to have this ability so that we didn't need to switch systems to create Pull Requests.
3 votesThis functionality was implemented in February 2022.
-
Add "Show selected" button to the Custom Filter editor
This button needs to be in the type and items columns. This way the developer will see the already selected components and be able to check faster if everything required is selected
1 vote -
User Last loggged in and User Usage
It would be great to see when a team member last logged in on the user account management page. It would also be great to see like a report or extension on the user page where we can see user usage information. Like number of compares, deployments, etc.. may when last compare was done.
23 votesTeam owners on the Automation Enterprise plan can find the last login time for each user in the CSV export on their account page.
-
1 vote
This is already supported as a [Named Item] under the [Setting] metadata type. Contact us in the in-app chat if you have trouble locating it.
-
Require Jira Ticket Before Validation or Deployment
We would like the ability to make the "Jira updates" section required (i.e. ticket selected) prior to validation or deployment.
2 votesYou can now require team members to link a Jira ticket before manual deployments and validations.
Simply, navigate to My Account -> Deployment Settings and enable the 'Require Jira Tickets' option.
-
Add support for the WorkSkillRouting metadata type
WorkSkillRouting is a key object in the configuration of Skills-based Routing for omni-channel (using Attribute Setup, not apex class), please add support for this object to enable comparison and deployment.
6 votes -
Include support for new metadata type 'PermissionSetGroup' (Winter '20)
As feature has moved from pilot to beta in Winter '20 release, looking for support in differencing and deploying the new 'PermissionSetGroup' metadata type.
20 votesYou can now deploy permission set groups in Gearset!
PermissionSetGroup isn’t included in the default metadata filter, so you’ll need to include it in any comparison filters you’re using.
Please get in touch if you spot any problems.
Thanks,
Tom -
Allow users with owner role to modify and start backups
Allow designated users the ability to modify and start backups without being the owner of the connected org or the person who created the backup.
5 votesYou can now specify other team members to have permissions to manage and start backup jobs they don’t own.
The current owner of the backup job will need to edit the current job settings, go to the new ‘Permissions’ tab and choose the team member and level of access that you’d like to grant them to manage your backup job.
-
6 votes
You can now add your on-prem GitLab instance to Gearset and set up validate pull requests with it. Thanks for your suggestion.
-
Cancel a running data deployment
Currently I am trying to copy data from production into a sandbox and mask them, but I forgot to adjust the amount of records to create. Now Gearset tries to create thousands of records for each and also mask them with a lot of fields included. I would like to abort the process but don't see any option because this huge amount of data and background services consumes a lot of time and compute resources. Also, I can’t estimate how much time is still left to complete the data deployment. Also, just to see is also a huge improvement but…
2 votesAdded on the 5th of October 2020.
-
Allow "View Errors" in CI Job History page to be opened in a new tab
It would be great if the button allowed to be opened in a new tab (essentially allow buttons and links to act like regular HTML elements that allow opening in a new tab via Cmd/Ctrl+click or via right click)
Example right clicking the "View Errors" shows no open to open in a new tab https://d.pr/i/m5CNIG
Right clicking "View comparison" allows for it https://d.pr/i/WpCfFF
This is similar to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/35538631-make-clone-package-openable-in-a-new-tab
1 vote -
Add support for Currency and Percent fields to be masked during a data deployment
We have some custom objects that hold financial data so masking currency and Percent fields will help when doing data deployments
1 vote -
Export subset of data in data backup
I would like to be able to filter what I want to export from a data backup, since I probably won't need everything from the database. This would make the downloading more manageable.
Ex: Export only ContactID and Email fields from Contact object from a specific backup.
(Restore data seems to allow this, but in this specific case I needed to run some checks in Excel since I couldn't just update everything with the old data)
3 votesYou can now select the object(s) to export for a particular backup run.
Simply go to the backup history for a job, and for a backup run, choose the ‘Download data’ option in the context menu to choose the subset of data that you’d like to export.
-
Support flow deletion at V44+
if the target flow is deactivated; and all prior versions are deleted, you can't delete the last remaining flow version in the target org. The error you get is "Insufficient access rights on cross-reference id".
Copado provides a solution (https://docs.copado.com/article/8l069zes9f-destructive-changes-in-copado-doesn-t-support-flow-and-process-builder) wherein the user can specify the contents of the destructive-changes.xml file (enumerating the versions to delete) but Gearset has no way to inject such a file into a compare/deploy (esp a CI deploy)
with SFDC pushing more and more dev into Lightning Flow, deletions are inevitable in many orgs as things get refactored/renamed
2 votesWe have added a problem analyzer that will detect when you are deleting a flow, and update the destructive changes xml to include all the versions automatically.
Thanks for the suggestion!
-
Resolve "Data Owner" User metadata from difference comparisons (always exclude or compare, then exclude)
Salesforce has begun adding User metadata to fields. One good example right now is the "Data Owner" field that appears on all custom fields now (in XML this field is labelled as "BusinessOwnerUser"). The field does not link via a Salesforce ID; it instead displays the Salesforce Username of the user.
Naturally, this field in 99.9% of Salesforce environment comparisons is going to be different. "user@domain.com.sandbox" won't ever match to "user@domain.com" in production-- and it definitely won't ever match to any other Sandbox, either.
This leads to a nightmare scenario where if this field has been…
5 votesWe have added a problem analyzer to detect and fix the issue with ‘businessOwnerUser’, as follows.
Problem: custom fields referencing a specific user will fail if that user doesn’t exist in the target.
Solution: this will replace the source ‘businessOwnerUser’ reference with the value from the target’s custom field.
-
Include a Comparison for a Permission Set Group's Muting Permission Set
Include a Comparison for a Permission Set Group's Muting Permission Set. Currently, you can deploy a Permission Set and/or a Permission Set Group. However, if that Permission Set Group contains a muting permission set, Gearset doesn't pull the data. Here is a link to the SF guide on the muting permission set: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mutingpermissionset.htm?search_text=muting%20permission%20sets
1 voteWe have now added support for this metadata type.
-
Remove botUser from Einstein Bot metadata
The metadata for EInstein Bots includes a tag called "botUser" that contains the username of the user you've specified to run the bot as. Because it contains a username, the deployment fails unless you have the exact same username in both environments.
My current workaround is to deactivate the bot, remove the running user (which removes the botUser tag), deploy, then reset the changes that I made.
Can we get a problem analyser that will detect and remove this botUser tag so that the deployment will complete?
1 voteHi. We have implemented a PA for this now, which will remove the BotUser field if needed to prevent Gearset from trying to overwrite the user with one from the source.
-
Upgrade to PMD 6.17.0
Current version is 6.11.0.
We should be consistent with newer version. We are having issues with older version in Gearset regarding the ApexDoc rule.
The issue was described and discussed with Valerio in the chat.
Thanks
7 votesWe upgraded to 6.21.0 today. Thanks for the suggestion.
- Don't see your idea?