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.
375 results found
-
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 -
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 -
Add link to test results in Microsoft Teams
Please add a link to the test results as part of the notifications sent to Microsoft Teams. The integration with Slack already includes the link so it would be very helpful to have a similar integration in Microsoft Teams.
4 votesThanks for your suggestion. I am pleased to say that the Microsoft Teams test monitor notifications should now have feature parity with the Slack notifications.
-
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.
-
Separate Filters for CI Jobs to reflect filter edits
Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.
It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.
6 voteshttps://docs.gearset.com/en/articles/618760-custom-metadata-filters-in-compare-and-deploy-and-ci-jobs
-
CI dashboard: Show commitId when job is in flight; Show queued commitIds
On CI Dashboard page, a CI job in flight (deploying/validating) should show the commitId that triggered it (if any) PLUS show all pending CI jobs.
Reason: If two developers are sequentially merging to a shared branch tied to the CI org (and webhook is setup to run immediately), then the first developer's merge starts CI job 1 while the second developer's job is queued.
Yet, from the CI job page there is no way to even tell which commit to the branch is running (so as to clue the developer that his/her job is running vs queued. Commit message would…
3 votesThanks for the suggestion! When a CI job is running from git, the commit hash and the commit message is now visible for all git providers. In addition, for GitHub, Gitlab and BitBucket sources, a link to go to the relevant commit will be displayed.
-
Github Pull Request as a `Draft`
This new feature is great. Would be even better if you can select that the PR be a draft.
1 voteHi,
You’ll now see the option to create a draft pull request in GitHub, if your repository supports draft pull requests.
Draft pull requests are available in public repositories with GitHub Free, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see https://help.github.com/en/articles/about-pull-requests#draft-pull-requests.
- Don't see your idea?