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.
1361 results found
-
test class not captured in deployment history
It would be nice to capture whatever test classes ran for code coverage deployment of classes/triggers in the deployment summary in the Test Results section. You already have a section for this test results so why not add the class names used in the report. We have come across many classes deployed without their appropriate test classes and it is hard tracking/documenting which test classes were used to deploy these as there are no documentations in the class.
6 votes -
6 votes
-
Allowing data deployments in CI jobs
Allowing data deployments in CI jobs. So that configurations in third party apps and B2B Commerce can be deployed as part of CI.
6 votes -
give the ability to ignore certain changes between Sandbox and Production enviornments
After deploying from a Sandbox to a Production environment, you will always see a 'change' for Custom Objects and Custom Fields because there is no Encryption Scheme (for example)
3 votes -
Changing executing time in a Job does not automaticalely start the Jobs!!
No information is given!!
1 vote -
Be able to start immediately a JOB (CI/Unit Tests/Monitoring)
Add a button to start it immediately. Currently only solution is to change the executing time!
2 votes -
See Continuous Integration Deployments in the Deployment History tab
List deployments resulting from a CI job on the Deployment History tab along with manual deployments.
We currently deploy metadata using both manual and CI jobs and it would be convenient to see all deployments in the same list (for debugging, reporting, monitoring).
4 votes -
edit other team member's CI job
Have a way to edit other team member's CI jobs, if appropriate permissions are given.
3 votes -
Show the Label as a column in the comparison screen
At present the comparison screen, Name column, only shows the information from the API name, but not the Label (as seen in Setup > Object Manager > Label column).
When the Label is wildly different from the API name, is would be super useful to have the Label displayed as a column, instead of having to find it in the XML viewer.
1 vote -
Show the latest commit(s) in the slack notification
It would be extremely useful for the development team to see the last set of commits which were deployed via an automated job, so that if it breaks it is easier to tell what broke the build or if it is successful what the org has been updated with.
4 votes -
Ability to search Deployment History for specific metadata
On the "Deployment History" tab, the filter dialog filters on the visible friendly name and items like that. What I would like to do is enter a specific metadata name and have the list filter down to deployments where that specific metadata name was a part of the deployment. This would be useful when getting the question, "when was xyz last deployed?"
14 votesIf we implemented this and it was only able to search metadata from that point in time onwards, would that be useful or would it be confusing to communicate in the UI?
-
Allow bulk org access for new users, new org permissions upon adding
When adding a new user having the ability to give the same level of access to all orgs at once would be greatly beneficial.
Likewise, when adding a new org and having the ability to set user access to the new org would save time as well.
We are adding new orgs frequently and will be adding users as well. Saving time on permissions would be great!
2 votes -
Run test in parallel using scratch orgs
CI job that run all test takes ages. Can we use scrach orgs and test suites to run test in parelell in multiple orgs?
https://developer.salesforce.com/blogs/2018/06/running-tests-5x-faster-using-sfdx-and-heroku-ci.html1 vote -
Add system log fields for created and updated operations for filters
It will be helpful if we know who/when a filter is changed. And it would be great if we could lock the filters as an owner.
1 vote -
Allow the ability to "uncheck" No DIfference items on the Selected Items tab
When cloning previous deployments, there are may cases where items may have been previously deployed, so the now would show as "No Difference". Currently these items can not be unselected for the deployment. It would be useful to be able to remove these from a current deployment to keep the deployment clean.
1 vote -
Adding Custom destructive
ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.
13 votes -
test Monitoring overview - show "is running" + stats
On the Test Monitoring Overview page; you should be able to see at a glance whether the test is running and how many methods have run vs total
Reason this comes up is if you establish a Unit Test run for your developer sandbox org, then you can't run (some) tests from your IDE against the same org "ALREADYINPROCESS Test already enqueued"
A quick glance at the Test Monitoring Overview would tell you if you need to wait 1 minute vs 20 - and guide your activities accordingly
2 votes -
Add default compare filter - Code changed by me today, changed by me last 7
A super common comparison done by a developer is to see only the Apex changes done by that developer today , or in the last x days
Since the last changed dates on Apex (VF, triggers, components) is super reliable whereas it is useless on Custom Field/Workflow), the suggestion applies only to Apex or code-type changes
Gearset would fetch only those code items changed in the last x days, then present in the difference viewer the changes pre-sorted in descending date order
This feature would eliminate multiple clicks just to deploy a handful of recently-made code changes in the comparison…
5 votes -
Support parallel testing during CI job
CI jobs use metadata API to deploy and run tests. The tests run serially. As such, CI jobs can take many minutes to execute
As an optional configuration for a CI job, and only if the CI is run against a non-PROD org...
- Deploy metadata using Metadata API
- Run tests using Tooling API (parallel testing)
- If tests fail, use MetaData API to rollback the deployment
Ideally, this can shave off 50% of the CI job time
2 votes -
Possibility to deploy to another sandboxe when a ci job passed
When configuring a CI job, we need an option to set a deployment to another sandboxe when the deployment or test classes run successfully in the current CI Job.
Ex: when a push to a branch on VCS triggers a CI job to deploy to a sandboxe like QA (with test classes run), we also have the possibility to set an auto deployment to staging sanboxe when the the job on QA passed successfully.5 votes
- Don't see your idea?