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.

I suggest you...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

1291 results found

  1. Add csv file results as attach

    attach a file to Teams after code analitics with incoming Webhook

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

  2. Add Comparison Column for "Environment"

    Add a column for "Environment" which signifies which environment the change took place. For instance, this would tell you whether the changes took place in Production Only, Sandbox Only, or both.

    Then, I could filter by Sandbox Only and both to see only the changes I made recently in the sandbox that I need to push to Production. Right now, I have to sift through the many little changes to items that occurred in Production.

    1 vote
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  3. Extend the functionality of configuring when are monitoring jobs run

    Hey,
    Currently it is possible to configure at what time during the day you we want to run the configuration jobs.

    For the org monitoring jobs, we really love that this is done daily, but for unit tests, we would love if we could configure the jobs to run the job weekly or monthly and not every day.

    1 vote
    0 comments  ·  Monitoring and reporting  ·  Admin →
    How important is this to you?

  4. Filter users for monitoring notifications

    Hey,

    Would be very beneficial if in monitoring tab, we could filter out users that we get the notifications about.

    For example, we don't want to receive changes that changes have been made in a Salesforce org if these changes are a deployment, but we would be interested to see if any users with Setup permissions are making changes to fields, objects etc.

    1 vote
    0 comments  ·  Monitoring and reporting  ·  Admin →
    How important is this to you?

  5. Require Jira Updates for certain types of deployments.

    While requiring updates on Jira tickets is nice we don't require this for ALL deployments such as if going to a production environment it's required however sandbox to github or sandbox to sandbox does not require an update.

    1 vote
    0 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?

  6. Ability to mark(starring or adding to favourites) deployed package for quick reference

    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.

    1 vote
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  7. Offer option to auto-limit items in clone comparison

    When a deployment is completed, you have an option to clone that package. For many of my deployments, I want to push a package to source control, and then on to production. The second comparison could be limited to just the items in the cloned package. Would be great to have an option to limit second comparison to only the meta-data items in the clone. Would allow subsequent comparisons to run much more quickly, if the user is confident that the package has everything needed for that specific deployment.

    1 vote
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  8. Option to ignore package namespaces differences in Apex classes

    Our Apex Classes reference multiple managed packages that are updated automatically in our sandbox/production environments. This causes many classes to get picked up unnecessarily in our comparisons/CI deployments between source control (where the managed packages are not committed) and org.

    Unlike https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/43917792-add-an-option-to-ignore-package-version-difference this is specifically for different package namespaces between the source and target.

    In this example the source has one namespace and the target has 2 package namespaces.

    It would be very useful to be able to choose to ignore all package differences in comparisons and CI jobs as a team-wide setting.

    1 vote
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  9. 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
    0 comments  ·  Problem analysis and deployment failures  ·  Admin →
    How important is this to you?

  10. 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
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  11. Increase the size of the 'Create new branch from...' modal.

    When creating a new branch from the 'Create new branch from...' model, it's hard because of the small size of the modal/dialog. Just sizing the modal/dialog larger would make it easier to work with.

    1 vote
    1 comment  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  12. 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
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?

  13. 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
    0 comments  ·  Monitoring and reporting  ·  Admin →
    How important is this to you?

  14. 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
    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

  15. 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
    0 comments  ·  Data backup  ·  Admin →
    How important is this to you?

  16. 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
    0 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?

  17. 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
    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

  18. 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
    0 comments  ·  Monitoring and reporting  ·  Admin →
    How important is this to you?

  19. 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
    0 comments  ·  Data backup  ·  Admin →
    How important is this to you?

  20. 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
    0 comments  ·  Comparisons and difference visualization  ·  Admin →
    How important is this to you?
1 2 … 49 51 53 … 64 65
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)