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.
1301 results found
-
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 -
Users should be able to specify test classes and save them to draft deployments
Users should be able to specific and save test classes in the comparison stage so they can be saved in draft deployments. Seems like a waste of extra steps to unclick tests and select tests over and over as you work through a deploy.
also when deploys are combined, they would get all the test classes, again, saving lots of time.
6 votes -
CI/CV job archiving
Create a mechanism by which CI and CV jobs can be archived, but not deleted. Sometimes there is a job that is not used, but the history needs to be kept for some period of time.
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 -
Display Permission Set changes as one entry
When working with Permission Set changes, it sometimes would be useful to see them grouped by Permission Set instead of being disaggregated by field. For example, we are migrating from using Profiles to Permission sets to grant all access. Currently, if we make changes to many (>100) fields in two different Permission Sets, we have to review many (>100) entries. Also, grouping by permission set would allow us to deploy changes to one Permission Set while ignoring the other.
2 votes -
Additional options for updating Azure DevOps work items
For example, we do not want to see messages posted for validation started, validation completed, deployment started, deployment completed. We only want to see messages posted on successful deployment. And one more thing is to update the State once the deployment completes successfully.
2 votes -
Add Analyzer to Warn/Remove Named Credentials with Passwords
Currently, attempting to deploy a named credential will fail as a "password is required for the specified authentication protocol".
This can mean manual work if you have a lot of CI deployment jobs to sandboxes or annoyance if you expected to be able to deploy it.
It'd be great if an analyzer existed that would alert/warn the user about it going to fail and unable to be deployed (suggest removing it from the package)
5 votes -
enable data deployment template merge
It is currently possible to select an existing template and add new objects and data deployment logic into it then save as a new template. It would save time to enable the selection of 2 existing templates and merge them into a single one.
1 vote
- Don't see your idea?