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.
360 results found
-
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.
-
Select more than one item at the same time
On "Items to include/exclude for Custom application" view, it would be really nice if we could select more than one item at the same time, using SHIFT shortcut.
When clicking on "Named Item", and if you want to select from the 49th line to 63th line for example, and to avoid to select manually 15 lines with 15 clicks.
We could just select the 49th line, and with SHIFT, click on the 63th line to select them.
Thx2 votesReleased on 10th of Aug 2022
-
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.
-
Deployment screen to show which components were selected vs included
When you get to the summary page, often times you will be deploying with the need for sub-components to be included in the package despite them being actual changes.
When you're selecting those items inside the comparison page, it would be helpful to see that total be reflected in the deployment summary page. So if you picked 50 items to deploy but it needed an additional 1,000 components (despite them having No Difference) then we should see those breakdowns on the Deployment Summary
Gearset soft alrt message "Some components with difference type of No difference have been added to the…
1 vote -
Refresh specific item in comparison through context menu
It would be great to refresh a specific item within a comparison that I know has changed since the last comparison.
107 votesGearset now supports:
- Refreshing a single item - available either from the context menu (by right-clicking an item in the comparison results table) or by using the "Refresh item" button in the XML preview window
- Refreshing selected items - available from the context menu once one or more items are selected
Thank you for commenting on and upvoting this request. We hope this new Gearset feature is going to speed up your workflow!
If anyone has feedback or suggestions, please contact us via the in-app widget.
-
Allow multiple Team owners to Connect to the bitbucket server through OAuth instead of creating a new link every time with in same Org
With in an org if we have multiple owners working as multiple teams, Gearset should be able to allow other owners to connect to the same Biibucket server through OAuth, instead of creating a new link every time.
3 votesThis was completed and released on 22nd of January 2020
-
Stop Reordering Package.xml
We would like to keep our package.xml file in alphabetical/lexicographical order by the <type> element. Gearset appears to change the order so that datatypes that include all <members> elements (i.e. use an asterisk) are placed at the bottom of the file. This inconsistent sort order makes datatypes harder to find when viewing or amending the file.
2 votesThis is now done. Thanks for the suggestion.
-
Deploy permissions for Lightning Record Pages
provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.
4 votesGearset now has precision deployments for Custom Applications, so you can select and deploy individual lightning page assignments.
-
Dependency Enhancement for App Menu metadata
Currently, when we compare App Menu metadata, the "Depends On" tree is empty, even though it definitely has dependencies on connectedApps and customApplications.
Please add dependency analysis for App Menu metadata,
1 vote
- Don't see your idea?