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

154 results found

  1. Add option to send notification to the Webex Teams for the Unit tests with the failed tests

    Add option to send notification to the Webex Teams for the Unit tests with the failed tests. While setting up a new unit test job for one of our Salesforce orgs I have observed that there in no option to send the notification to the Webex Teams chats. It would be critical to our org as we use Webex.

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

  2. Add the ability to put CI jobs into folders

    It would be great if we had the ability to put ci jobs into folders. We've accumulated a number of CI jobs. Some of these jobs are no longer in service and we're a bit reluctant to delete them as they may have historical information that we may later want or need. It would be great to be able to put things like this into folders to help reduce clutter and organize our CI jobs page. thanks for your consideration.

    6 votes
    2 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?

  3. 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?

  4. 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?

  5. Add Salesforce Data Cloud sandboxes as an option for deployments

    Salesforce Data Cloud sandboxes are now generally available but to promote changes from sandbox to production, the only options are through Data Kit and change sets, CLI, or DevOps Center. Having the option to use GearSet would be helpful so all deployments were managed the same.

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

  6. Clickable Jira Request within Pipeline Promotion History

    I would like the ability within the pipeline promotion history to make the Jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.

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

  7. enable using a Repository Access Token instead of a Service Account

    I would like to be able to use a repository access token instead of a service account to connect to VC (Bitbucket in my case). https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/

    The main benefit for me would be the ability to conveniently authenticate while maintaining a high level of security, even in situations where corporate change management policies and SSO requirements can be cumbersome.

    3 votes
    2 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?

  8. jira comment after deployment

    Right now gearset posts comments to Jira when validation is completed and PR is merged.
    We would like to have comments also when deployment is completed.

    The current comment "Successfully merged PR #297 from gs-pipeline/SF-23601-preprod into preprod" tells nothing to business users, they are not aware of git, CI/CD and what this message means.
    Comment "Deployment to preprod is completed" makes much more sense for them.

    5 votes
    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?

  9. Allow configurable default settings for Jira integration

    Allow us to customize the default behavior for the Gearset<>Jira integration. Currently, Gearset posts a comment on the linked Jira ticket every time a commit is started and completed. This creates a lot of noise on the ticket.

    Currently the only way to customize the messages posted to Jira are on a ticket-by-ticket basis. Allowing an option to customize this at the org/pipeline level (e.g. only post a comment when a deployment succeeds) would be very helpful.

    3 votes
    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?

  10. Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates.

    Allow configuration of where pull request/merge updates are posted in Jira. User comments are being missed because of the volume of updates from Gearset when moving a set of changes through the pipeline. These updates are important and we want to keep them, however having the ability of moving them to another tab/section on the Jira ticket would mean we could keep the comments section for user comments only.

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

  11. Make the commit hash clickable in Pipeline PR Commits tab

    This is rather trivial, but also seemingly a quick-win.

    In the Commits tab on the Pull Request details screen in the Pipeline, make the 7-character commit hash a hyperlink that opens a new tab into github.

    It is minor, would save me 1's of seconds, but it seems like an easy win - the commit url is just {{git-origin-url}}/commit/{{7-char-hash}}

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

  12. Notify when PR is automatically created (e.g. back propagation)

    Notify the developer when a Pull Request is automatically created. For example when next pipeline stage is reached and a PR is automatically created or when a back propagation PR is automatically created.
    A comment in related Jira ticket would be very helpful.

    4 votes
    1 comment  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?

  13. Update assignee for jira tickets

    According to our team flow once feature is deployed to UAT environment, linked task in Jira must be reassigned to QA team lead to start testing.
    Right now this is completely manual process.
    It would be nice if we can specify assignee in gearset pipeline settings.

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

  14. Provide ability to link ADO ticket after a package has been validated

    It would be great to be able to attach/link ADO ticket after a package has been validated. Currently we can only do it before click the validate button

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

  15. Update Jira Status when linking to a ticket in Gearset

    When a Jira ticket is linked to a branch in Github through Gearset, the status of the ticket could be automated (For example, we have statuses of In Development or Ready for Pipeline which could be used) to match further with the automatic status changes when the feature deploys through the pipeline.

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

  16. Let "member" re-authorize team-shared orgs connections

    In our Gearset setup, we have tens of "Team-Shared" orgs, both production and sandbox. Whenever any sandbox gets refreshed, its connection in Gearset needs to be re-authorized.

    Currently, only users with "Owner" role have this "Re-Authorize" option. Users with "Member" role don't have this option.

    This creates a problem for my team. Since my offshore team is supposed to do these sandbox refresh and re-authorization tasks, and they can't do it unless I give them "Owner" role, and thus giving them admin privilege over the entire Gearset.

    Thus, I'm looking for a way to let a non-owner re-authorize salesforce org…

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

  17. Customizable Messages for Jira Ticket Associations

    When a Jira ticket gets a new comment from a validation or deployment, it's a pretty standard message:

    Deployment succeeded: link...etc.
    Deployment Notes:
    Source: ----
    Target: ----
    And then a table of differences that were pushed through.

    My thing is, none of this is customizable, whereas I'd love to be able to potentially change what's automatically appended to our tickets to make it more user-friendly for the reporters on those tickets.

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

  18. Add "View Validation in Salesforce" to your Github and Teams/Slack Channel messages.

    Our pipeline is utilized by some implementation partners that we do not give access to Gearset. They manage their changes that flow through the pipeline with GitHub and receive pipeline updates in a Teams channel. Both of these options have a message to view validation errors in Gearset but the partner teams cannot see Gearset. If these messages included the same "View Validation in Salesforce" option that lives in Gearset, they could be redirected to the Salesforce error page to help their troubleshooting faster.

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

  19. Delete feature branches in Github in a way that they can be restored

    I closed a PR to master, and Gearset deleted the feature branch. However, it wasn't merged, so I wanted to restore it to continue work. I was completely gone from Github. I believe Gearset should do a normal delete that allows restoration instead of completely obliterating feature branches or allow an option to do so.

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

  20. Enable us to customize the Slack notifications from Gearset

    Enable us to customize the Slack notifications from Gearset (e.g. add deployment Friendly name to Slack deployment notifications). Thanks

    6 votes
    3 comments  ·  Integrations and connections (Jira, source control, DX etc.)  ·  Admin →
    How important is this to you?
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Help us improve Gearset

Categories

Feedback and Knowledge Base

(thinking…)