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.
1357 results found
-
Allow masking of State and Country to recognize API values
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.1 vote -
Store List of Objects Downloaded in Data Download History
Given that the actual download files for Data Download expire after a short amount of time (which is completely logical), it would be beneficial to be able to know what objects were included in the data downloaded, and potentially any filters used.
The main reason behind this is from a security stand point, if an employee with access were to go rouge and decide to download sensitive data to sell/take with them, there is no way of telling what kind of data they may have if you were to miss the window of the backup being available.
1 vote -
Notification of unresolved CI job failure
As the owner of the CI job pipeline, I would like notifications when there are ongoing failures to the CI jobs that I select so that I do not have to continually monitor the jobs as a part of my day-to-day.
Acceptance criteria:
- The current-state suite of notifications on CI jobs will still be available.
- When a CI job has failed and the failure has not been cleared within X number of hours, the notification will be triggered.
- Each CI job should have blocker notifications enabled separately.
- Users will be able to select from SMS, email or both.
- Users will…
1 vote -
Gearset Scratch Orgs: Generate Passwords
Our team would like an enhancement to how Gearset handles generating scratch orgs from authorized Dev Hubs. We want to be able to provide log-in credentials to non-gearset users in order for them to use these scratch orgs and perform development work.
We want our deployment manager (gearset user) to manage the provisioning of scratch orgs and the retrieval of changes in these orgs to source control. Our developers currently just focus on developing features and are abstracted from the complexities of the deployment process.
To make this process a lot simpler for our deployment managers, it would great to…
2 votes -
Add a Select All that works on filtered items when setting up filters
When setting up the filters, I would like the ability to do a Select All on just the filtered items so that I don't have to manually select each one of them. This would be a huge time saver.
10 votes -
Replicating Data should include backups as a source
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.
1 vote -
Allow team member to create unit test job based on the shared connection
I try to create the unit test job but the org connection is available to me even it is shared to me with the deployment permission. I have to either create a new connection or let my colleague who is the owner of the connection do it now,
Thank you!
1 vote -
Ability to compare data between two backups
It would be great if you could compare data between two backups. Currently you can only see what has changed since the last backup.
1 vote -
Show how big a data deployment is going to be when deploying, as some Salesforce sandboxes have a limit of 1GB
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
3 votes -
Ignore "trackHistory" comparison if an Org has "FALSE" and Git does not define this entry
The Salesforce CLI system returns the Custom Field Metadata XML file without a "trackHistory" entry if it is set to false. This XML entry is optional in the Custom Field metadata type. However, once we deploy such metadata to the org and execute compare between a branch and the org again, it shows differences, saying that "trackHistory == false". But is "false" by default. So I would recommend you ignore this entry if SF Org returns FALSE and the VCS file does not have this item.
1 vote -
Filter Deployment History by Source / Destination
At this time, there does not appear to filter deployment history by specific orgs AND other criteria in the general "filter" text box. I would like to find specific packages deployed to a specific org and also that have a standard friendly name. I am only able to enter text to filter by the friendly name and the additional filters allow for source / destination type, but it does not allow for specific source / destination.
2 votes -
Create a Data Deployment Template for migrating Territory Management (1.0 & 2.0)
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.
3 votes -
Add option to provide exact time in case automatic deployment
We need to set exact time for automatic deployment. We need this option for example for night releases for specific client. This is important for international clients that works in different time zones
2 votes -
I want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structure
I want to be able to share 'delegate org access' with other team member(s) so they can visually see our security / deployment structure for reporting.
In this example the fact that "user A owns the connections and has delegated the permission to user B" is not visible to user C. Ideally user C would be able to see that delegation information for auditing purposes.
1 vote -
8 votes
-
Include validation rules and triggers of managed packages in 'Compare and deploy disabled rules'
When configuring a data deployment there is an option to disable validation rules and triggers on the target org. However the validation rules of objects of a managed package don't get included in this comparison. Triggers of a managed package are also not included.
I'm not sure if it will be possible to disable the triggers, but for validation rules this should be possible.
3 votes -
1 vote
-
APEX Class Change
APEX Class Changes Reporting
It would be really cool if, through the monitoring side, if a summary Excel could be created. Excel could have multiple tabs: 1 tab per class change with four columns:
col1 :original line #
col2: original line value
col3: new line #
col4: new line valueHeader could include change DateTime, source/target orgs, Gearset ID, who, etc
Thanks
Ron1 vote -
Preview of records for data deployment
It would be great either via the UI or a downloadable file/CSV, if we could see all the records that will be migrated in the data deployment. We're able to see the list of successful or failed records after the fact, it'd be nice to see the list of proposed records before hand. This would help identify if we're in the correct ballpark, say 500 records vs. 5000, and not knowing that until after the deployment gets attempted.
4 votes -
Deactivate email deliverability on Data Deployment
User email are masked in Sandboxes and we can mask Contact emails as part of the data deployment. This still leaves the Org Wide addresses as valid emails. If there is automation that is generating emails related to the data that is loaded, they will be delivered to the Org Wide Addresses.
It would be useful if the same script that is deactivating validation rules could set email deliverability to systems emails at the same time.
In the even that email deliverability was set to all emails in the Sandbox and not adjusted before the data deployment we would have…
5 votes
- Don't see your idea?