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

347 results found

  1. Deploy permissions for Lightning Record Pages

    provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.

    4 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

    3 comments  ·  New feature  ·  Admin →
  2. Introduce 'ListView' as an option in 'Metadata filter' tab

    When navigating to the 'Metadata filter' tab to select filters, there are currently 122 options, however 'List View' is not one of them.
    When navigating 'Metadata Types & Components' in Workbench, 'ListView' is described independently, and I have used it previously when deploying via ANT. Therefore I would imagine there is a way to identify List Views independently of 'Custom Objects'.
    This would be a huge help with a Production monitoring job, as I do not mind if List Views are updated by certain users in Production, but currently they are flagged as differences. Basically, I want to ignore them…

    27 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

    7 comments  ·  New feature  ·  Admin →

    This is now released, you will need to update the metadata filter for any jobs set up already to take effect.
    You can now exclude list views as well as other subcomponents of custom object.
    (Note: named items is not populated for subcomponent metadata types.)

  3. Documentation around ramifications of deleting a connection (and possibly an Archive option)

    I haven't seen anywhere in the support documentation that details any ramifications (if any) when deleting a no longer needed Salesforce connection in GearSet.

    The kind of ramifications I'm thinking about are:

    • Validated Packages based on the connection, could I still review/clone/deploy?

    • Deployment History - will all information still be available? Can I still clone from a previous deployment?

    • Comparison History - can I pull up a previous compare?

    etc.

    If there is any negative impact to the above, then it would be appropriate to have an "Archive" option for Salesforce connections. The thought with this would be one, the…

    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

    Hi Jonathan,


    I have written a document detailing what happens when a connection is deleted. 

    You can view it here - https://docs.gearset.com/en/articles/7882840-deleting-an-org-connection.


    Thank you for your feedback and please do tell us if there is anything I've missed out.


    Quinn Kuiper

    Customer Success at Gearset

  4. Unique filename of the generated report PDF

    Currently, the name of the generated PDF file of the deployment report is always the same for a given source and target.

    If we deploy from our "master" gitlab branch to our "production" environment, the name will always be the same.

    We archive the report PDFs for documentation / compliance reasons, and we always have to manually rename the PDF file to make the name distinct.

    It would be nice if the name of the report PDF was unique. This could be achieved by either including a timestamp or the deployment number into the filename.

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  5. Update package.xml with destructive changes which helps CI jobs

    When I commit components to bitbucket brach if I have 5 new components and 5 deleted components. then Gearset is updating package.xml in the src folder with only 5 components which are to be created but destructive changes are tracked no where. Then if we deploy from this branch changes to Sandbox using CI job which has 'Filter metadata changes using package.xml' checked, then the deleted components will not be deployed. It is good if Gearset give a feature to track destructive changes and deploy using CI job.

    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

  6. Deploy CMS/CRM Connection and and CMS Collections

    We would like to be able to deploy CMS/CRM Connection and and CMS Collections. They are a part of Community Workspace.

    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

  7. Select more than one item at the same time

    On "Items to include/exclude for Custom application" view, it would be really nice if we could select more than one item at the same time, using SHIFT shortcut.
    When clicking on "Named Item", and if you want to select from the 49th line to 63th line for example, and to avoid to select manually 15 lines with 15 clicks.
    We could just select the 49th line, and with SHIFT, click on the 63th line to select them.
    Thx

    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 →
  8. Support integration with OKTA

    Salesforce orgs that have OKTA as a SSO Identify Provider cannot seem to be connected to Gearset using SF Authentication. Therefore is makes it impossible to do Monitoring and Tests.

    Please look into supporting OKTA SSO

    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

  9. Add an option to disable the "repository sanitizer"

    The "repository sanitizer" performs unsolicited/silently changes which confuse users and generate issues. For instance, if you have Apex class permissions in profiles for classes which are part of a managed package and are not present in the repository, this sanitizer will modify the permissions to false which is obviously a disaster, (and the changes can happen any moment, while users are trying to deploy something completely unrelated hence the confusion).

    We know the solution is to have the classes also in the repository but for managed packages that's unnecessary extra work since then we need to be updating them every…

    12 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

  10. configure which problem analyzer results to use in CI jobs

    Being able to configure which problem analyser results to use in CI jobs.

    For instance, we can’t deploy any changes to managed packages because the problem analyser will ignore them (even though we have components from a managed package that we can modify and deploy without issues), that would help to reduce our manual steps during deployments.

    46 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

  11. List the unit tests failures in the email notification being sent out

    Currently, when the unit test job fails, we can view the test history and results by going to the web page. However, we would like to view the summary of unit tests that failed in the email notification that is being sent out.

    9 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

    Completed  ·  2 comments  ·  Testing  ·  Admin →
  12. Allow multiple Team owners to Connect to the bitbucket server through OAuth instead of creating a new link every time with in same Org

    With in an org if we have multiple owners working as multiple teams, Gearset should be able to allow other owners to connect to the same Biibucket server through OAuth, instead of creating a new link every time.

    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

  13. Support the CustomHelpMenuSection metadata item

    We use the CustomHelpMenuSection item to customise our Help & Training dropdown list in Salesforce, and we would like to include it in our deployments automatically.

    It's been available in the Metadata API since version 45, but Gearset doesn't appear to support it yet.

    Will it be available soon?

    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

    Completed  ·  0 comments  ·  New feature  ·  Admin →
  14. Add Failure Information to CI Job's Email Notifications

    Currently, Unit Test jobs provide a nice email notification of what tests failed right in the email body.

    CI jobs, however, provides the same generic message for failures for validations as below:

    "The validation only CI job, Release Validation, has failed. Find and fix the validation issues on the error summary page in your CI job history"

    and for CI deployments

    "A continuous integration job, Prod to Dev3, has failed. No changes were deployed to the target org.

    Find and fix the deployment issues on the error summary page in your CI job history. "

    It'd be great to get…

    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

  15. Allow Updating of Associated Jira Ticket Statuses on Successful Deployment

    With Gearset's current the ability to associate a deployment with Jira tickets, and post updates as comments to the stages of deployments, the ability to choose the status (from what is defined in the status of the Jira Board), upon a SUCCESSFUL deployment, would be incredibly helpful in our environment plans for our projects.

    By being able to select the status to update all tickets to from the Jira board, we could effectively manage our custom stages for different projects.

    22 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

  16. Add link to test results in Microsoft Teams

    Please add a link to the test results as part of the notifications sent to Microsoft Teams. The integration with Slack already includes the link so it would be very helpful to have a similar integration in Microsoft Teams.

    4 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

  17. Add batch size option to data deployment

    It would be great to be able to pick the batch size used when doing data deployments.

    We have to work with some orgs using poorly performing managed packages that are blowing up due to CPU limits.

    We don't have many option, so being able to reduce the batch size, and hence the CPU load would be really useful.

    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

  18. CI dashboard: Show commitId when job is in flight; Show queued commitIds

    On CI Dashboard page, a CI job in flight (deploying/validating) should show the commitId that triggered it (if any) PLUS show all pending CI jobs.

    Reason: If two developers are sequentially merging to a shared branch tied to the CI org (and webhook is setup to run immediately), then the first developer's merge starts CI job 1 while the second developer's job is queued.

    Yet, from the CI job page there is no way to even tell which commit to the branch is running (so as to clue the developer that his/her job is running vs queued. Commit message would…

    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

    Thanks for the suggestion! When a CI job is running from git, the commit hash and the commit message is now visible for all git providers. In addition, for GitHub, Gitlab and BitBucket sources, a link to go to the relevant commit will be displayed.

  19. Improve Bitbucket Server integration for teams with large number of project/repositories

    ideally... gearset should not be hitting https://adlm.nielsen.com/bitbucket/rest/api/1.0/repos
    first. It should hit https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects to get a list of projects
    then allow the end user to select the project
    then https://adlm.nielsen.com/bitbucket/rest/api/1.0/projects/{projectKey}/repos to get a list of repos on the project the end user selects

    12 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

  20. Stop Reordering Package.xml

    We would like to keep our package.xml file in alphabetical/lexicographical order by the <type> element. Gearset appears to change the order so that datatypes that include all <members> elements (i.e. use an asterisk) are placed at the bottom of the file. This inconsistent sort order makes datatypes harder to find when viewing or amending the file.

    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

  • Don't see your idea?

Feedback and Knowledge Base