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
-
Allow export of code coverage results in daily Unit Testing job
It would be great to be able to export the list of unit tests and their respective code coverage in a csv file for further internal processing.
2 votes -
Update Metadata Change Monitor Report
When you update the change monitor report metadata filters and include new metadata types, the next monitor report shows all the newly added metadata as "New Items" on the report. Although not a big deal it did cause an alarm for us not realizing it was due to the change we made prior. It would be a "nice to have" feature if either you don't include the newly added metadata types as "New Items" on the initial report or flag them and have a visible cue to indicate the items were a result of newly added metadata items on the…
1 vote -
Global Search feature
It would be very useful to have a Global Search feature within Gearset. This would be used to search the contents of all metadata objects.
My use case is that sometimes a string has been hardcoded inside a function. The only way to find the function that contains the string is to manually trace through the code. The global search would indicate the function that contains this string.
Another benefit would be to track dependencies for metadata objects that don't support dependency tracking. For example Aura Components, we could search for the component name.
12 votes -
Added an 'Or' function to the Filter Options
Right now there is only an 'And' filter when configuring Fields on the same object. It would make this much more powerful of a tool if we were able to chose between 'And' & 'Or'.
5 votes -
Connection List Search Feature
Add a Search feature to Connections Page. I have 59 connections at the moment and the only differentiation between them is a suffix at the end of the login. It would be nice to be able to quickly search the list of Connections like a CTRL + F would do.
I often have to scroll the list and compare login usernames.
2 votes -
Allow orgs to be grouped in folders
On the “My Connections” page, I'd love to see an option to add a folder (and sub-folders).
Currently, there are options for "Developer orgs", "Sandbox orgs", "Production orgs", and "Scratch orgs".
If you are running more than one entity, having the sandboxes related to a single entity inside of a folder would be more user-friendly than having multiple dev/sandbox orgs inside the same folder.
For example, if I'm managing deployments for "ABC Company", "XYZ Company", and "LMNOP Company", and each has multiple sandboxes, it would be really convenient to be able to separate out their various sandboxes more effectively, into…
2 votes -
Force selection of fields to use instead of selecting id as default
In the select related objects page, Gearset selects id as the 'fields to use' field. If we are deploying a large set of data and by mistake do not change the 'fields to use' field then we end up creating duplicate records for Upserts. Would be great if there is an option to enable or disable the default selection.
1 vote -
For failed CI job runs, develop a way update to the job status
When for whatever reason, jobs can get job stuck in status "Deploying".
The real deployment task is already successfully finished in the org, so I would expect that the status of the CI job would be "Succeeded".
I was assured that in 24hrs the status of the job will automatically reset, but can we have also a way to force an update to the CI job manually?
Note: The "Cancel running CI job" button is visible and clickable, but doesn't do anything with this stuck CI job.
1 vote -
SFDX projects and source format and CLI useage
Gearset CI only supports SFDX source that follows the SFDX project template structure (e.g. force-app/main/default/classes and so on). However, SFX CLI doesn't mandate that structure.
SFDX allows you to group metadata by function or logical group (so you can combine metadata in any way that makes sense to you) . We have many projects like this that gearset cannot deploy.2 votes -
Ability to modify pieces of data before deployment of data
E.g when you want to move data from PROD to DEV there are some fields (e.g. Contract Status) that you want to move from Active to Draft. This should be a generic function also to be applied to other fields / objects.
2 votes -
Gearset to be added to a connect app
The ability to use Salesforce as an Identity Provider and have gearset be added as a connected app so the user would be forced to sign in with SSO and select when they sign in from salesforce
1 vote -
1 vote
-
Add capability to export components as part of the full deployment history export
It would be good if we were able to export the individual components that were part of a deployment when we export, say, the full deployment history from the past 6 months, or all time.
This would help with IT audits.3 votes -
Archive or hide Automation jobs
On each of the Automation dashboard views (Monitoring, Unit testing, Continuous integration) it would be nice to have a way to archive or hide job. Often times previously setup jobs that are not active but would be good to keep for historical reference can clutter the dashboard.
6 votes -
Show the name of the draft I am working on
Would be nice to see the name of the draft I'm working on while I'm working on it. Oftentimes working on multiple things at once, this can get really confusing.
1 vote -
Rename drafts after they're created
It would be really nice to be able to rename drafts after they've been created. Sometimes users will name things differently, and it would be nice to be able to clean this up.
1 vote -
I would like the ability to change filtered metadata to their API names
I recently had an internal business conversation to clarify what would and wouldn't be included in our new CI/CD process leveraging gearset to push to orgs. When we had this conversation we used the Metadata API names to discuss and then when I went to implement it in Gearset I saw that the filters are actually some translated 'friendly' names.
This is of course fine for most use cases, but it made it really difficult to make sure nothing is being missed when setting up the CI/CD filter type.I would kindly ask that you implement some switch to allow…
1 vote -
Unable to import/export translations using .stf file using greaset
Currently gearset allows to deploy translations from one org to another org, however we do not have an option to do the translations using .stf file /excel for the fisrt time in any one of the org
1 vote -
Make Data Deployments Invocable (Salesforce APEX)
As a feature to enhance data deployments, make them invocable by Salesforce APEX (or other tooling) whenever a Sandbox is refreshed. Salesforce has a configuration to let the user specify an APEX trigger/class to run upon Sandbox creation. That could call the data deployments to run on the freshly minted sandbox, seeding it with data. This would enhance automation.
There are tools out there (like SFApex) that do something similar.
1 vote -
add the ability to filter Git repos on connection
It would be useful to be able to select only applicable Git repos from source control that will interact with Gearset. A user may have many repos that they need on their account, but of those there may only be 1 which would be used via GearSet. It would be great if we could select which repos should be available when setting up the connection to our source control (specifically I am requesting GitHub but I think this would be useful for all source control integrations).
2 votes
- Don't see your idea?