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.
1150 results found
-
Validation Failures - Show Error in Table
In the new UI for Validation to view failed test classes error messages you must click into each failed class to view the details.
The previous UI showed "part" of the error message within the table. This was extremely useful in identifying all of the "unique" errors that are occurring.
IE: If 58 test classes fail from "4" unique issues -- then in order to determine that you may need to click into all 58 test classes or fix one at a time --> refresh --> validate.
This is just a time save feature.
1 vote -
Show history of changes for a component
When performing forensic analysis regarding how or why something started working differently, it would be a great timesaver to be able to select a component and then be able to select the data comparisons for just that component. For example, select an apex class and then pick date dates so the system can display what changed. I would expect that this would be quicker than going into Monitoring Histories and picking each date and waiting for it to build the entire comparison of everything that changed and then having to find the component of interest.
A follow on to this…
1 vote -
Remind repo owner to upgrade metadata on SFDC version change
Your blog post https://gearset.com/blog/mdapi-versioning-and-version-control says it all under the paragraph labeled "Upgradingyour repository's metadata"
But there's no real reminder to tell the team that this is a meritorious idea. My suggestion is that for the first 30 days after PROD is updated, you could display (in color) some alert (or maybe introduce a messages feature) wherein you tell the team that the repo's package.xml is out of date (version wise) with PROD version and provide pointers on how to upgrade, including nuances like Flows (v44).
It is too easy to get lazy and leave the repo metadata out of date…
1 vote -
Enable Defaults or Recently Used on Clone Deployment Page
When you clone a deployment package you have to select your Source details, but the selections do not default to the the last used settings or to a recently/commonly used settings. This is a minor annoyance but in other parts of GS you have the last selected options already selected based on user history, so hoping you can extend this to the Clone page
1 vote -
Export snapshot of production org to git
I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.
After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.
For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.
1 vote -
Jira: Updating existing tickets with deployments using the standard Atlassian smart comment format
"[TicketID,...] some comment"
1 vote -
Target Process Integration
Agile/sprint planning tool similar to JIRA
1 vote -
Selection Count Mismatch
The Selection count on ‘Compare and Deploy’ page doesn’t match with ‘Items Selected’ on ‘Draft Deployment’ when a draft deployment is opened. Having this in sync will help user that all selections are going in the deployment.
1 vote -
Be able to exclude single items from comparison
E.g. If I generally want to include all Custom fields for all Objects in the comparison, but there’s one specific field that I don’t ever want to send across to the target org, it’ll keep popping up and I’ll have to uncheck it each time.
1 vote -
Track Items Added to Draft Packages
It would be nice to be able to see which items within a comparison are part of Draft Packages. We have a need to build multiple packages from a single Comparison of Instances. This can be done by creating many Drafts, but it is sometimes difficult to know if items have been added to a draft package already. If we could visually see this, it would allow us to generate and confirm our packages much faster.
1 vote -
Ability to set a friendly name to the package
Should it be possible to set an equivalent of "friendly name" in Gearset but one that can also be spread to Saleforfce.
1 vote -
Changing executing time in a Job does not automaticalely start the Jobs!!
No information is given!!
1 vote -
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 -
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 -
Deployment count in the blue banner wrong for old deployments
When viewing old/past deployment details, that old deployment shows me the big blue banner saying that ---this--- was our {insert total number of deployments ever}th deployment no matter which old deployment I'm viewing.
This confused me a bit because I wanted to view our say 5th deployment ever so expected the number to say this was our 5th deployment, and I ended up closing the details browser tab twice thinking I pressed the wrong button to view the latest deployment. Yeah I could have looked at the tiny timestamp somewhere on that details view, but this large blue banner/counter just…
1 vote -
Make "Clone package" openable in a new tab
In Deployment history, there are two buttons I use the "view details" which I can open in a new tab without leaving the list of deployments, and the "clone package" which I can't open in a new tab. I can workaround it easily (duplicate tabs, or first view details then clone from there), but it was disappointing that I have to.
I needed to re-deploy say 10 deployments into a different sandbox and so the clone package feature was amazingly useful, but this little nag prevented me from entering the blissful nirvana of wielding the perfect tool for the job…
1 vote -
When running "Compare and Deploy", or via a similar mechanism, allow the target to be a local zip
In rarer situations where I need to make some manual adjustments to the metadata XML for a deployment, I'd like to be able to download the metadata to adjust it. Today you need to go through a compare, and at the end, you can download the package, but this can be problematic, since you have to choose the target org, there need to be differences, etc.
Instead, it would be useful to just choose the source org, select the metadata items, and save the package, without a target org needed.
1 vote -
Pending Validation - Copy from Pending Deployment
Similar to "Pending Deployments" It would be nice to see pending validations. We have several users in gearset, so if we are trying to validate something while someone has already initiated a validation, we receive the error that set up has been locked. So prior to validating a package, it would be great to check if anyone is in the process.
1 vote
- Don't see your idea?