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
-
List the unit tests failures in the email notification being sent out
Currently, when the unit test job fails, we can view the test history and results by going to the web page. However, we would like to view the summary of unit tests that failed in the email notification that is being sent out.
9 votes -
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
-
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 -
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
-
Allow Updating of Associated Jira Ticket Statuses on Successful Deployment
With Gearset's current the ability to associate a deployment with Jira tickets, and post updates as comments to the stages of deployments, the ability to choose the status (from what is defined in the status of the Jira Board), upon a SUCCESSFUL deployment, would be incredibly helpful in our environment plans for our projects.
By being able to select the status to update all tickets to from the Jira board, we could effectively manage our custom stages for different projects.
22 votes -
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.
-
Add batch size option to data deployment
It would be great to be able to pick the batch size used when doing data deployments.
We have to work with some orgs using poorly performing managed packages that are blowing up due to CPU limits.
We don't have many option, so being able to reduce the batch size, and hence the CPU load would be really useful.
8 votesThis now completed and can be set at a team level at https://app.gearset.com/account/data-settings
-
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.
-
Improve Bitbucket Server integration for teams with large number of project/repositories
ideally... gearset should not be hitting https://adlm.nielsen.com/bitbucket/rest/api/1.0/repos
first. It should hit https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects to get a list of projects
then allow the end user to select the project
then https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects/{projectKey}/repos to get a list of repos on the project the end user selects12 votesGearset will now filter by project first when selecting a repo/branch for Bitbucket Server
-
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.
-
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 -
Compare and Deploy Attachments and Files
Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!
19 votes -
Scratch orgs - Create a new scratch org with more than one package
During the creation of a scratch org the system doesn't allow the installation of more than one package...so after create a scratch org we need to install manually the remaining packages.
6 votesYou can now install more than one package when creating a scratch org.
-
Ignore Unlocked Package Metadata In Comparisons
Currently, metadata from Unlocked Packages show up when comparing against an org. This leads to duplication of metadata in source control repositories (correct DX package repository and incorrect monolithic, "happy-soup" repository).
Using the Package2Member Object (Tooling API), it is possible to deduce whether or not a metadata item is part of an unlocked package. Therefore, it should be possible to ignore some or all unlocked packages (or any Package2 package), in a similar fashion to the way Gearset filters allow inclusion or exclusion of managed packages.
17 votesIn comparisons, all metadata from unlocked packages is included by default. However, some users wish to exclude unlocked package metadata from a comparison. This is so that they don't have to see metadata that they don't need to consider for their deployment.
So we’ve added this ability!
Within the packaging sidebar on the right hand side of the large filter, there is now an option to Exclude unlocked packages from a comparison. Shown in brackets is the number of distinct unlocked packages identified across the two environments.
-
Report CI validation/deployment status to source control
When a CI job is triggered by a commit to source control, please update the source control system with the result of the build - so that e.g. with Bitbucket we could see the build result from pull requests as at https://confluence.atlassian.com/bitbucket/check-build-status-in-a-pull-request-945541505.html
4 votesGearset will now report CI job statuses to both Bitbucket and Bitbucket Server
-
Update CI Job History Exports to include User and DateTime Stamp
In the CI Job section under the view history button, when selecting the ability to export the changes, Is it possible to include a DateTIme stamp
and User column for each row change?10 votes -
Ability to run a Validation only CI job on a pull request - this will make pull request ready for deployment without error
- Developer creates a pull request to a branch
- CI job validates the pull request and notify in case of errors
- Developer corrects errors - CI job again validates the pull request and this time it is fine 4.Release manager merges the pull request to the branch specific to an org and CI job deploys without error.
9 votesWe now support validating pull requests from GitHub, GitHub Enterprise, Bitbucket, Bitbucket Server, GitLab and Azure DevOps.
-
Add Prompt metadata type
Please add the new Prompt metadata type
1 vote -
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 -
Add support for incoming webhooks
There's already a way to set up an outgoing webhook after a successful CI job run.
It'd be nice to have a way for a CI job to have an incoming webhook from another service, such as ElectricFlow (a build platform).
One use case would be for CI deployments to be dependent on external validation services.
4 votesThis is now possible since we have released our API, which is available to everyone with an Enterprise license! Please see https://docs.gearset.com/en/articles/6099550-getting-started-with-the-gearset-api for more details. If anyone has feedback or suggestions, please contact us via the in-app widget.
- Don't see your idea?