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.
369 results found
-
Update package.xml with destructive changes which helps CI jobs
When I commit components to bitbucket brach if I have 5 new components and 5 deleted components. then Gearset is updating package.xml in the src folder with only 5 components which are to be created but destructive changes are tracked no where. Then if we deploy from this branch changes to Sandbox using CI job which has 'Filter metadata changes using package.xml' checked, then the deleted components will not be deployed. It is good if Gearset give a feature to track destructive changes and deploy using CI job.
1 voteCompleted on October 29th, 2020
-
Deploy CMS/CRM Connection and and CMS Collections
We would like to be able to deploy CMS/CRM Connection and and CMS Collections. They are a part of Community Workspace.
1 vote -
Ability for team members to manually run the CI
Currently, only the owner of the CI job can manually run the CI. If the owner is out or unavailable, this creates a problem for team members because they have to deactivate the current job, clone and setup the new CI OR transfer ownership. Transferring ownership doesn't work if a team member is out unexpectedly, ill or doesn't have access to perform the transfer.
It would be helpful if you could grant access to a group of team members who have access to manually run the CI. This would save a lot of time and prevent having to keep multiple…
14 votesWe have made changes to the app on the 29th of June release for Enterprise licensed Gearset users:
Added the ability to run CI jobs belonging to other users if the source is a git repo and the target has deployment access delegated.
We think this now covers the cases:
- Allow an enterprise licensed user to run other people’s org to org CI jobs
- Allow an enterprise licensed user to run other people’s git to org CI jobsWe have not implemented allowing user to run other people’s org to git CI jobs. As this is sub use case is quite a specific interpretation of the original suggestion. Perfectly happy for it to be specified in another separate suggestion.
We have updated the documentation to reflect this change – https://docs.gearset.com/en/articles/2533179-access-levels-in-gearset
I hope this delivers the what your team needs. Feedback always welcome :)
-
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.
-
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 -
Test Run results
Test Run results show duration in Seconds but I believe the results are actually in Milliseconds
2 votes -
Correctly create Price Book Entries records with different currencies and updated PBEs when they are out of sync (or delete+insert)
1) Currently PBEs are incorrectly inserted with the company currency as apposed to the currency of the source record.
2) PBE's currency cannot be updated once created (SF restriction) but because PBE's should not be referenced by Id, (that would be a terrible design decision). It is quite possible to delete and recreate any out of sync records.
16 votesHi, this feature has now been implemented. You should now be able to deploy PricebookEntry records with multiple currencies when you select the “Create new records” deployment option
-
Add support for CMS Connect Sources
Please add support for CMS Connect Sources in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Connect in our current developments of a customer community and we'd like to deploy this metadata as well.
See the metadata api documentation: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_cmsconnectsource.htm2 votesWe have now added support for the CMS Connect Source metadata type.
-
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.
-
Treat "New" FLS entries that don't grant any access as "Not Different" in Profiles and Permission Sets
Due to a recent change in the SF API, Permission sets now display every field in the org as a "New" FLS item, with Readable and Editable both set to False. This is leading to two distinctly negative results.
1) For every "Permissions for FieldNameXXX" item, every permission set in the org is modified. If two projects on two different sandboxes each add a field, they will both modify modify all the same files, and require manual XML merge. for our org thats almost 70 files that need manual merge with every new field.
2) When you dig into a…
3 votes -
Allow Team Members to Run Scheduled Unit Test Jobs
Execute Others’ Unit Tests
John Doe creates daily unit test job for SuperHeros R Us. He schedules it to run nightly.
Jane Smith, a member of the same Gearset team, is responsible for doing the weekly deploy for SuperHeros R Us. The unit test job from the previous day has failed (it had been previously working). Jane makes updates to the tests, and needs to re-run the unit test job. But she does not have permissions and John is out on PTO for the day. So… she needs to do it manually.14 votesReleased on December 31st, 2020
Test monitors can now be run by anyone who has validation access to the org being tested. -
Documentation around ramifications of deleting a connection (and possibly an Archive option)
I haven't seen anywhere in the support documentation that details any ramifications (if any) when deleting a no longer needed Salesforce connection in GearSet.
The kind of ramifications I'm thinking about are:
Validated Packages based on the connection, could I still review/clone/deploy?
Deployment History - will all information still be available? Can I still clone from a previous deployment?
Comparison History - can I pull up a previous compare?
etc.
If there is any negative impact to the above, then it would be appropriate to have an "Archive" option for Salesforce connections. The thought with this would be one, the…
1 voteHi Jonathan,
I have written a document detailing what happens when a connection is deleted.
You can view it here - https://docs.gearset.com/en/articles/7882840-deleting-an-org-connection.
Thank you for your feedback and please do tell us if there is anything I've missed out.
Quinn Kuiper
Customer Success at Gearset
-
Show start time, end time and duration of a data deployment
This would be very helpful in order to communicate and set expectations with others on how long Data Deployments take as well as seeing how to improve the speed of longer running Data Deployments. If only one date/time can be displayed, then I think it would be better to see the End Time of the Data Deployment job. Currently, the Date column listed appears to be either (1) the start time of the Data Deployment job, or (2) the date/time when the Configure and deploy was clicked to start configuring the job. If it's #2, this isn't very useful.
2 votesThe data deployment history page now shows the start time, duration and end time (on hover) of a data deployment. The start time is the start of the deployment (option 1 that’s listed here).
-
Support the CustomHelpMenuSection metadata item
We use the CustomHelpMenuSection item to customise our Help & Training dropdown list in Salesforce, and we would like to include it in our deployments automatically.
It's been available in the Metadata API since version 45, but Gearset doesn't appear to support it yet.
Will it be available soon?
1 vote -
Associate pull requests to work items in Azure DevOps
When you create a pull request from gearset, the pull request isn't associated with the Azure DevOps work item.
9 votesWe've enhanced Azure DevOps (ADO) integration! You can now associate work items with pull requests directly through the ADO sidebar.
This improvement leverages ADO's native features for a more seamless and efficient workflow.
-
Add Failure Information to CI Job's Email Notifications
Currently, Unit Test jobs provide a nice email notification of what tests failed right in the email body.
CI jobs, however, provides the same generic message for failures for validations as below:
"The validation only CI job, Release Validation, has failed. Find and fix the validation issues on the error summary page in your CI job history"
and for CI deployments
"A continuous integration job, Prod to Dev3, has failed. No changes were deployed to the target org.
Find and fix the deployment issues on the error summary page in your CI job history. "
It'd be great to get…
1 voteReleased
-
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.
-
Support integration with OKTA
Salesforce orgs that have OKTA as a SSO Identify Provider cannot seem to be connected to Gearset using SF Authentication. Therefore is makes it impossible to do Monitoring and Tests.
Please look into supporting OKTA SSO
2 votesThis is supported. You can select a Salesforce authentication method and click on [Use Custom Domain] to achieve this. See https://docs.gearset.com/en/articles/2131749-does-gearset-support-sso for more detailed steps.
-
Allow users to discard chunks/certain changes before deploying to target
For example I'm on the diff screen and I see my page layout has 5 changes/chunks of changes, but I only want to commit/deploy the first one - please add functionality so that I can discard/ignore the other 4 changes in the file and only deploy the one change I want.
5 votesYou can now exclude fields and other items in page layouts from being deployed using Gearset's new Precision deployments feature: https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
-
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.
- Don't see your idea?