Currently, user is able to select Obj A, Obj B that references Obj A, Obj C that references Obj B. And, in the next step of data deployment it allows user to select Objects where Obj A, B or C, and objects references by those objects.

If we ignore above example, I want to be able to select: objA(id), objB(id, objA), objC(id, objB, objD), objD(Id), objE(Id, objD). Where the first object I select and everything else is filtered on is objA.

Currently there is no field mapping option available for Data Deployment of Objects. This is a big blocker if we want to migrate selective fields data across Salesforce instances.

"invalid or null picklist values" is thrown and i have too many picklists to figure out which one is the issue. Please provide speicific fields that are causing errors.

The Salesforce Import Wizard has an option to not trigger any automation during data jobs. It would be fantastic if Gearset provided such an option.

This would include:
- Workflows
- Process builders
- Flows

I know this feature already exists for validation rules and triggers.

Data deployments should ask if you want to Insert or Update or Insert & Update data.

Currently it always performs data upsert only

With the deprecation of Worfklow Rules, I'd love to have the disable Rules include the active Flow Definitions

This feature would allow me to setup each sandbox environment after doing a refresh from production.

I think a great feature would be for the tool to be able to copy all object data from one org to a sandbox, and if the amount of data is too large for the sandbox, allow the user to specify what objects to take sample data from - and how - i.e. take no data from a certain object,or take 5% of the latest created data, etc. It would be helpful to show the objects that have the most data.

While it is nice to deploy record data from org to org with Gearset, it would also be nice to be able to deploy data from a CSV file, with the ability to custom map the headers. Native Salesforce Dataloader has this capability, as well as many 3rd party tools out there. Please incorporate this capability into Gearset.

when Deploying metadata and linking it JIRA Issue it will be a good idea to have more Jira Issue fields visible not just the Jira Issue key(id).l would like to have Issue "Summary" field Visible

Once the deployment is done, if i want to clone the same pkg after 2 months, then its difficult for me to search through. Instead if there is any way to mark it by adding a star to adding to any favourite list will make it more handy and also available for quick reference.

If the State and Country lists have been updated so the API values are set to ISO country codes the Masking of those fields during a data deployment does not work.
Data Load errors: '"FIELDINTEGRITYEXCEPTION:There's a problem with this country, even though it may appear correct. Please select a country/territory from the list of valid countries.: Billing Country:BillingCountry --"'

Disabling masking works around the issue.
It would be great if the application could check the State/Country list and utilize the API values for masking.

Currently you can only push to 1 Salesforce org, however, we manage multiple organizations and would like the capability to push the same package to multiple organizations

Currently its possible to replicate data from a backup job by going into the backup run and clicking replicate data.

However, this is extra steps... its would be good if you could just select backups as a source from the data deployment screen.

I suggest you have functionality to show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB

I would like to see a gearset defined template for Territory Management in Salesforce. I am definitely in need of this functionality as it seems to be a post deployment step once you deployed all Territory Management metadata.

in ETM 2.0 for example, after deploying the related metadata you need to deploy all related records for UserTerritory2Association Object, this contains who are the users assigned to a territory.

Not a big template but can be a good thing to have as a preset.