Skip to content

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.

If you need any further support, please contact us at team@gearset.com.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1130 results found

  1. to let us configure the default metadata filter by deployment pipeline configuration

    Can we please have a possibility to configure the "standard" metadata filter by each deployment pipeline project?

    I think it is currently preselected by the last used metadata filter from the standard comparison.

    As we usually have a specific metadata filter configured by deployment pipeline project, it would be great that we can configure each project with a default one..

    Thank you!

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Test salesforce connections in mass to highlight which need to be re-authorized

    Having a way to monitor/test all salesforce connections in mass to then highlight which need to be re-authorized would be helpful instead of catching them when preparing to do a comparison.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Possibility to validate a feature branch as a whole without having to select the Metadata type

    It looks like the current validation jobs setup in Gearset needs the Metadata Type to be explicitly selected to perform the validation. This should ideally be optional and there should be a capability to just validate everything that is there in the feature branch against the target org. It's really annoying for us that we have to select the Metadata Types to be validated.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Force-deploy Flow translations with no difference

    At the root of this, the main problem is that if you create a new flow version through the SFDC flow editor interface, the flow will have a new version of the flow translations based on the previous translations.

    But if you DEPLOY a flow, the new flow version is created WITHOUT flow translations at all.

    This would be fine, if gearset would allow us to reliably deploy the flow WITH flow translations, even if the flow translations had "no changes". (Gearset does not allow us to deploy items with no change, and sometimes doesn't even show them in the…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add Time Column to the CI Deployment page

    Due to recent latency issues regarding SF performance issues, I would like to quickly see how long each CI job takes without having to download an individual report for each job. This can either be solved by either:

    1. Adding a field to the CI Deployment page so that I can compare each CI job

    2. Allow me to extract a complete report of all of the CI jobs and open it in excel with the time column so that I can compare the values. I can currently do this from the Deployment history page, however this does not include the CI…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Support deployment of password and session policies via Gearset

    According to the Salesforce developer link https://help.salesforce.com/s/articleView?id=000349181&type=1

    Password and Session policies include a numeric code which is equal to a epoc timestamp. This timestamp will be different in each org. In order for deployment to succeed, the timestamp code in the metadata name must match the target org. Since all orgs are different, there isn't an automatic way to do this.

    Please create a feature in gearset that will automatically replace the timestamp numeric code with that of the target org so that we can use gearset to deploy password and sessions policies.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Data Deployment Template that supports complex rules

    Looking to be able to setup a Data Deployment template that supports complex rules with record limits.
    For example...
    - Select 100 accounts that have been modified recently that belong to division A that contain at least 1 contact, 1 opportunity and 1 activity.
    - Select 100 accounts that have been modified recently that belong to division B that contain at least 1 contact, 1 opportunity and 1 activity.
    - Select 100 accounts that have been modified recently that belong to division C that contain at least 1 contact, 1 opportunity and 1 activity.

    Currently have to build 3 or…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. change monitoring for scratch orgs

    The Change Monitoring feature only supports normal orgs (sandbox, developer, prod). It does not support scratch orgs

    For use cases where developers inadvertently let their scratch org expire with pending, uncommitted work, it would be nice to recover the work before and after the scratch org expires

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. BitBucket commit on a successful Org deployment

    It would be a nice feature to have a setting on the deployment summary page to also commit to a git branch with deploying to an org.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Allow owners to setup delegated org access of members

    Without already having delegated access granted there is no way to rollback a deployment from another user. There should be a permission to override this.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Exclude OmniStudio generated LWCs for CI

    Currently OmniStudio will generate LWCs for it's flexicards and OmniScripts.

    We want to have CI syncing in to a repository, however we don't want to have these autogenerated LWCs in the repository. This is code that users won't be modifying themselves, isn't constructed to be read by a human, and will actually be controlled by the Vlocity elements that GearSet already supports.

    Reviewing the metadata produced by omnistudio, it seems that all the LWCs produced have the runtimeNamespace tag in their meta.xml file set to 'omnistudio'. It would be ideal if we could filter out all LWCs with that tag/value…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Show "All" Different Items

    Instead of a tab showing 'All Items', even items that are the same, maybe show a tab of All Different Items, which would show New, Deleted, and Changed in a single view without having to sift through the 'All Items' for these.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add option to load missing dependeces only.

    Example:
    When I already selected metadata filter with many items, downloaded metadata, compared, checked, and clicked deploy then I am getting an error that some dependency is missing but it is metadata type that wasn't selected previously.

    Currently:
    I need to click refresh comparison select additional metadata types and reload all metadata from both sandboxes. It is very time and resource consuming with big packages.

    As a solution:
    I want to have the possibility to click a button and select on the metadata list only those that I want to add to the current package and only those should be…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Manually Delete Metadata after CI job runs

    We don't want the CI job to delete metadata, so we've unchecked that box. However, when a CI job runs that would have deleted data, we'd like to be able to select from the job history, review what would have been deleted and elect to deploy the deletion manually post CI run. We can re-run the comparision from Compare and Deploy, but having this action tracked within the CI job history would be more convenient, and would allow the history for the target org to be contained in the same thread.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Users with access to same target org

    2 users both have access to the same target org with different user accounts. User A creates a package and asks User B to deploy the package on their behalf. Unless User B has been delegated access to the same org they already have access to by User A's account then User B will be unable deploy the change as they receive the error

    "To deploy you need deployment level permissions from the owner of the target"

    Workaround to this security constraint was to download a copy of the package and deploy using Workbench.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. whenDeploying metadata and linking it JIRA Issue it will be good idea to have more Jira Issue fields visible not just Jira Issue key(id).l

    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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Support Email Template Folder metadata migration

    Metadata API for EmailTemplateFolder does not accept wildcards so you have to know the name of the folder to be able to pull it down and migrate it. Currently (as of 2-16) the Gearset product cannot pull these.

    Suggest that they add functionality to make a SOQL call to get all the folder names, at which point they should be able to pull them. Allowing for compare and deployment.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add tool to send emails after deploying to specific targets

    A project manager on my team expressed desire to receive reports when someone deploys to our production org. I would appreciate a tool that sends these emails only upon successful deployment to that specific org so that recipient's inbox is not flooded with every successful and failed deployment to every org.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Record/file level filters for Backup jobs

    Allow Backup job filters to be configured for specific records/files rather than entire objects.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. API to export backup to S3 for data warehousing/datalake

    A lot of time we would like to have data out of SF not just for backup purposes but for data analytical purposes as well. Ownbackup currently has this functionality via APIs.

    https://documenter.getpostman.com/view/12146739/TzJuAxgY#0f1fc918-7616-4b58-8d52-0e8370f57d9b

    https://ownbackup-kb.magentrixcloud.com/articles/knowledgebase/Using-the-OwnBackup-API-5-6-2020

    If gearset has this, it would help us move to GS for all our SF problesms

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base