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.
150 results found
-
Trigger a Gearset CI deployment from an Azure DevOps release approval event
Right now Gearset supports the set up of webhooks into azure devops which trigger deployments when a branch is updated.
I'm looking for an extension to that feature to also include "approval completed" steps. These are already available to hook into within Azure DevOps, so I'm hoping it'd should be a relatively small piece of work to extend GS to support this
4 votes -
Show JIRA Title when selecting tickets to post to
As a release manager, when I go to select the JIRA tickets to associate to, I need to be able to see not just the ticket number, but also the Title to allow me to select the correct tickets without having to guess or consult another resource or use trial and error.
Currently there looks like this idea was implemented in Pipelines, but that interface is somewhat broken, and typing in the full number does not result in the ticket showing up, could use some love, but is the right idea for providing context.
1 vote -
Create GitHub App as alternative to GitHub OAuth
Gearset currently uses OAuth to connect to GitHub, and the way that works is that the OAuth connections have permissions to all repositories that my user has access to, which from a security perspective is a problem, because if the github key were ever compromised, it would provide very broad access to customers GitHub organizations.
Security teams would feel much better with the ability to limit the scope of access to just one repo instead of all the repos that my GitHub user has access to, which can be accomplished by creating a Github App which can be installed for…
10 votes -
Show JIRA issue summary when attaching a JIRA issue to a deployment
when Deploying metadata and linking it JIRA Issue it will be a good idea to have more Jira Issue fields visible not just the Jira Issue key(id).l would like to have Issue "Summary" field Visible
2 votes -
Create JIRA ticket when CI Job runs sucessfully
I undrestand that gearset can update status, comment and attach report to an existing JIRA ticket once a deployment is successful, but it would be nice to have a feature that would automatically create a JIRA ticket once the CI Job runs, and deployment is successful, for reporting and internal auditing
1 vote -
Ability to Template Scratch Org Settings
It would be great if it was possible to template the scratch org creation screen.
We have a lot of managed packages that need to be installed and having to enter the ID and Key every time is very time consuming.
1 vote -
provide the ability to add tags to branches within Azure DevOps.
Within Azure Devops you can group commits and changes into a release based on a tag. So for a user to be able to add that tag when they are associating a workitem to a commit would mean they didn't have to go into Azure Devops later to add the tag.
3 votes -
enable linking two separate gearset accounts when they are hooked to the org
I've been using Gearset for a few years. The Salesforce consultant I occasionally work with just started using Gearset with all their clients. So we both have a connection to my Salesforce org. It would be nice to see a combined view of deployments, validations, test runs, etc. made against my org - regardless of which Gearset account it was done from.
1 vote -
enable linking two separate gearset accounts when they are hooked to the org
I've been using Gearset for a few years. The Salesforce consultant I occasionally work with just started using Gearset with all their clients. So we both have a connection to my Salesforce org. It would be nice to see a combined view of deployments, validations, test runs, etc. made against my org - regardless of which Gearset account it was done from.
1 vote -
When creating a Pull Request from Gearset have the option to default to another branche
After you did a deployment from a sandbox to GIT (Github in my case) you have the option to create a Pull Request right from that screen. The default target branche is "main" even though my default branche in Github is set to develop.
It would be great if Gearset follows that default branche that is set in Git OR has a way of defining default target branche in Gearset.
The risk now is that someone might overlook this, make a pull request against main, someone else also overlooks this and merges it into main. With CI jobs on main…1 vote -
Additional feature - GITHUB Pull Request validation in CI Job
Checkbox - Pull requests: Validate pull requests targeting the source branch is only visible when Run Job is set to --> Run tests based on Apex changes in the package
Request you to enable option even when this is set to Run Job: 1 / 2 /4 / 24 Hours
1 vote -
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 -
Ability to mark certain branches as your favorite branch so you can pick them quickly
When selecting a branch from source control, it would be great if Gearset had an ability to mark certain branches as favorites so they appear the top of branch selection dropdown.
3 votes -
Gearset configuration as a Code (git or exportable)
Gearset configuration as a Code (git or exportable) so that there is a way to store it i.e. in Git and see how various jobs, cicd pipelines, monitoring and schedulers are configured which is an enterprise way to implement solutions nowadays (PaaS, IaaS etc..)
2 votes -
Add ability to disable all comments on JIRA tickets
Currently, when adding a ticket number in JIRA connector on a deployment, there is no possibility to disable comments sending on JIRA.
This can be a problem, as JIRA tickets can also be seen by our final users, and this "XXX has deployed the ticket" kind of comments can question them.
3 votes -
Connection List Search Feature
Add a Search feature to Connections Page. I have 59 connections at the moment and the only differentiation between them is a suffix at the end of the login. It would be nice to be able to quickly search the list of Connections like a CTRL + F would do.
I often have to scroll the list and compare login usernames.
2 votes -
SFDX projects and source format and CLI useage
Gearset CI only supports SFDX source that follows the SFDX project template structure (e.g. force-app/main/default/classes and so on). However, SFX CLI doesn't mandate that structure.
SFDX allows you to group metadata by function or logical group (so you can combine metadata in any way that makes sense to you) . We have many projects like this that gearset cannot deploy.2 votes -
Gearset to be added to a connect app
The ability to use Salesforce as an Identity Provider and have gearset be added as a connected app so the user would be forced to sign in with SSO and select when they sign in from salesforce
1 vote -
add the ability to filter Git repos on connection
It would be useful to be able to select only applicable Git repos from source control that will interact with Gearset. A user may have many repos that they need on their account, but of those there may only be 1 which would be used via GearSet. It would be great if we could select which repos should be available when setting up the connection to our source control (specifically I am requesting GitHub but I think this would be useful for all source control integrations).
2 votes -
Additional options for updating Azure DevOps work items
For example, we do not want to see messages posted for validation started, validation completed, deployment started, deployment completed. We only want to see messages posted on successful deployment. And one more thing is to update the State once the deployment completes successfully.
2 votes
- Don't see your idea?