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

1129 results found

  1. Offer the ability to set the ignorewarnings flag on an individual "Compare and Deploy" basis.

    Would like to see the ability to set the IgnoreWarnings as an override for an individual Compare and deploy, in addition to at the global level. Occasionally, we will do a community deploy, for example, that returns a warning about a page that includes a Dashboard component, with the warning that the Dashboard ID or the Filter ID might not exist in the target environment. Once we see those errors in the validation results, it would be convenient to rerun the deploy, and ignore those warnings. Possibly similar to how the Test execution options are set on the Deploy button…

    3 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. Apply certain PA outputs back to the comparison as a "quick fix"

    The main example where I have wished for this pretty strongly is the "missing permissions" PA. This is the one that warns "not all permissions are included in the deployment". It would be useful to be able to go from that PA to a view where one could either add all the missing permissions in one go, or do so selectively by profile or permission set. Right now one has to screen scrape the output, paste it into a text file, go back into the comparison and laboriously hunt through the comparison to find the missing nodes, then add them.

    1 vote

    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)
  3. Granular "difference types to deploy" on a metadata level

    In the CI job, we would like to have the ability to specify on a metadata level if we want to deploy new items, update items and delete items. There are examples of metadata where we always want to delete and others where we don't want to.

    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. Create new branch using type-forward / auto-complete from JIRA (or other supported tool)

    It would be great if you have JIRA connected, to make it easier to create your branch. So basically type-forward (-ish) functionality to identify a JIRA ticket and take the issue ID and description as branch name.

    Say your JIRA ticket is ISSUE-1234 Implement this awesome feature.

    The default branch name would be issue-1234-implement-this-awesome-feature.

    (Where it reads JIRA could be Azure or any other support tool of course).

    1 vote

    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. Prevent Accidental Backing Out of Deployment components when Deploying Multiple Packages

    Sometimes I have multiple packages that have been validated, that I am looking to deploy. If they happen to overlap components, then deploying in the wrong order could back out a change made by the earlier deployment.
    From this I came up with two ideas that could help:

    1) The ability to select multiple validated packages or draft deployments, and click a button that will tell me if they have overlapping components. That will let me know if I have anything to worry about; if they overlap then maybe I should combine them into one package.

    2) The ability to…

    1 vote

    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. Allow Deployment Notes to be editable post-deployment

    Allow Deployment Notes to be editable post-deployment. Our team uses very specific notes for auditing purposes, and being able to edit them post-deployment would make that process a lot easier for our teams.

    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. Production/Sandbox Backup job color

    The backup job color (or a colored tag) should be introduced so you can clearly see which backup job is for Production and which is for a Sandbox.

    At the moment they all look the same and you have to make sure you are clicking on the correct one, only by looking at the username to understand if it is a Production org or not.

    This is confusing and risky

    1 vote

    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)
  8. Allow serial deployment instead of parallel

    When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
    Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
    For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
    If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.

    6 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. Restrict visibility for monitoring jobs

    I would like to be able to monitor daily changes made without those monitoring jobs being visible to the entire team. We have some super motivated people as well as the other end of that spectrum. I would like to have some data to visualize daily without the entire team seeing what I am doing.

    1 vote

    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. Select All Option in Deployment history

    It would be nice if we have the select all option in the deployment history to select multiple packages to combine in one go and deploy as one package into target.

    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  ·  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)
  11. The ability to deploy only certain fields in a record type and not all fields

    If we want to promote a change to a single field in a record type, we're unable to because the file is pushed in it's entirety. We'd like the ability to view from list of available changes in a record type by field and select just the changes to the fields we want to promote.

    3 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. Change the Metadata Filters and make them first class

    I would like to see a change to the metadata filtering in general.
    Filter management has become a important part of our devops process as we seek to lower our comparison timing.
    Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
    In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy

    5 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)
  13. Rename the Name bar in compare and deploy to : Name (api)

    Simple to implement, just a string rename...
    Rename the Name bar in compare and deploy to : Name (api)
    It would show clearly that the name displayed there is the API name, not the "label" name XD
    Cheerio

    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. Include code coverage in deployment report

    Hi,
    I want to use the deployment report to monitor your progress towards improving the quality of our code.
    So I need code coverage to be included in this report.

    6 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. Add option to make picklist fields non-restricted before performing a data deployment

    Similar to being able to disable validation before performing a data deployment it would be very useful if there was an option to automatically uncheck the "Restrict picklist to the values defined in the value set" option for some or all of the picklist fields in a deployment.

    We have data that includes picklist values that are no longer active this causes errors on individual records as part of the load. Currently I have to pick through all the errors manually then uncheck the option for the corresponding picklists fields on the target org. Then after performing the deployment I…

    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. Enhance Metadata Filter Type Recognition

    Our team has struggled learning the Metadata API names of metadata types when compared to what items are called in change sets. One example would be to highlight Weblink when a user searches for Button.

    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. Option to ignore: <personAccountDefault> in XML

    When comparing XML for RecordType permissions in Profiles, some Sandboxes return:
    <personAccountDefault>true</personAccountDefault>

    As part of the XML, even though person accounts are not enabled, this makes comparing annoying.

    It would be nice to have an option to ignore this.

    8 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. 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

    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 deployment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    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. 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:

    1. The current-state suite of notifications on CI jobs will still be available.
    2. When a CI job has failed and the failure has not been cleared within X number of hours, the notification will be triggered.
    3. Each CI job should have blocker notifications enabled separately.
    4. Users will be able to select from SMS, email or both.
    5. Users will…
    1 vote

    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)
  • Don't see your idea?

Feedback and Knowledge Base