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. Create a functionality which can Export all the Open PRs for Pipeline

    Dear Gearset Team,

    We recently encountered a challenge where we had approximately 250 open PRs in production. To streamline the process, we needed to submit a report listing all open PRs, which were then reviewed by the Dev team. If a PR was deemed unnecessary, it needed to be declined. Additionally, some tickets were withdrawn, which required the associated PRs to be declined as well.

    Currently, this task requires us to manually open each PR, copy the PR link, add the story linked to the PR, and include the assignee of that story. We then input all this information manually…

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

  2. Adaption of Deployment frequency of CI jobs

    While setting up a CI job, I recognized there are only automatization options up to every 24 hours, which is once a day. Currently there is no possibility to deploy e.g. every second day or even more important to us, every week/ every second week. Please add this possibility when adding CI jobs, to have a slower Deployment cycle to e.g. demo sandboxes, that don't need daily deployment.

    1 vote
    0 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?

  3. Add stacktrace column to Test Outcomes

    There is no Stacktarce information on the Test Outcomes from the Unit Testing page. That information is important to help the developer team investigate the issues.

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

  4. Audit history on Data Backup Jobs

    For SOX compliance, we backup our Salesforce production data with Gearset. However, there is currently no way to determine the last time the job was modified. If at the bare minimum we had the last modified date & the user that modified the job, we would be able to confirm for the auditors that no changes have been made. Ideally, we would have tracking on the job for the different features - adding or removing objects, cadence of job, etc. For now, we're having to do a manual review.

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

  5. Add testing steps to Jira ticket

    Like the new feature for adding pre/post deployment steps, it would be good to be able to add testing steps to a feature in gearset.

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

  6. I would love to be able to edit the name of a feature while it is in progress in the pipeline.

    We include the release date as part of the feature title, but sometimes the release date changes after we create the feature and while the feature is still in the pipeline. It would be great if we could update the name of the feature at any point up until deployment to production.

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

  7. Add Pre/Post Deployment steps for Data deployments

    Some data deployments require manual steps pre and or post deployment.

    Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,

    1 vote
    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

  8. Add Pre/Post Deployment steps for Data deployments

    Some data deployments require manual steps pre and or post deployment.

    Scenario we had was that a rule for whatever reason couldn't be turned off by GS so I had to manually switch it off or the deployment failed then back on after it deployed,

    1 vote
    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

  9. Audit changes to the "Require issue tracking" setting

    As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.

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

  10. Audit changes to the "Require issue tracking" setting

    As a result of a query by our auditors it would be helpful to have changes to the 'Require issue tracking' deployment setting audited. They are concerned that a team-owner could alter this to perform a deployment then reinstate it, resulting in change deployment without tracking.

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

  11. Show doesRequireRecordChangedToMeetCriteria on Flow Navigator

    The doesRequireRecordChangedToMeetCriteria toggle on flow Decisions doesn't show on Flow Navigator, making it harder to check for issues on builds when using the comparison tool.

    doesRequireRecordChangedToMeetCriteria should show in the flow navigator, same as the rest of the decision configuration.

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

  12. Fix comparison default date range

    1. Click new compare and deploy
    2. Select a source and target.
    3. Notice the date range says "Today" but DON'T change it.
    4. Click Compare
    5. Notice the date range now says "All Time"

    Repeat...
    1. Click new compare and deploy
    2. Select a source and target.
    3. Notice the date range says "Today"
    4. Change the date range to anything else
    5. Change the date range back to "Today"
    6. Click Compare
    7. Notice the date range now says "Today"

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

  13. Fix pre/post deployment steps from disappearing.

    1. Add Pre or Post deployment step
    2. Click "Specific environments only"
    3. Click the "x" to remove all the environments Notice, the entire "Environments to run against" section disappears To get it back you have to cancel, and do it again.
    1 vote
    0 comments  ·  Bug  ·  Admin →
    How important is this to you?

  14. Add Omnistudio Features to Scratch Org Features list

    When using the 'Create new scratch org' screen the following features are not available in the 'Scratch Org features' list

    OmnistudioMetadata
    OmnistudioRuntime
    OmnistudioDesigner

    These are available features according to the Salesforce documentation

    https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file_config_values.htm#so_omnistudiodesigner

    1 vote
    0 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?

  15. Allow IN Operator for Data Deployments

    When filtering for specific records with ID's, would be handy to have an IN operator for record selection.

    1 vote
    0 comments  ·  Data deployment  ·  Admin →
    How important is this to you?

  16. Problem Analyzer while building the deployment

    Surface problems with building the deployment to allow users the correct in the deployment.

    1 vote
    0 comments  ·  Problem analysis and deployment failures  ·  Admin →
    How important is this to you?

  17. Feature that allows users to post Deployment information to custom object in Salesforce

    Gearset has feature to allow users to send depolyment information to Jira. Provide the ability to do the same to a custom object in Salesforce.

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

  18. Please add 'Type' and 'Priority' field from Jira to Reporting API.

    In the absence of 'Type' and 'Priority' field from Jira in Reporting API, it become significantly challenging to report on Cange Failure Rate and Mean Time To Resotre and rely on either on the Jira title or description, which is again a heavy lifting in order draw the report.

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

  19. Force API update for deployment

    Please provide the ability to force API versions for deployments.

    Allow the administrator to place an API version in a setting and when a deployment is validated or attempted deploy if the API version is the value or below then do not allow the validation or deployment.

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

  20. Trigger CI Jobs on Gearset deployments

    When setting up a CI Job originating from SFDC, we only have the option to trigger the job based on a time interval. Which makes sense since there are no events to subscribe to in SF for this.

    But, I think it'd be helpful to be able to trigger a job to run on the completion of another Gearset deployment. This would be useful for automating the addition of metadata items like fields or layouts into source control, which are less-than-fun to create as xml files.

    So rather than running such a job every 1hr, we'd ideally be able to…

    1 vote
    0 comments  ·  Deployment automation  ·  Admin →
    How important is this to you?
1 2 … 35 37 39 … 64 65
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)