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.
119 results found
-
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..)
1 vote -
Allow upload of Scratch Org Definition file from VCS
On the "Create a new scratch org" page -- since SFDC recommends that Scratch Org definition files go in VCS (see https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm)
then the Upload dialog should offer an option to browse repo/branch/folder for the desired Scratch Org Definition file (default path would be main/config)
and, once selected, the other portions of the page that are overridden by the Scratch Org definition file should be both populated and disabled so the user gets a confirmatory echoing of choosing the right scratch org definition file
1 vote -
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.
3 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 -
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 -
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.
2 votes -
add static code analysis results to pull request
Can you add the ability to add the static code analysis results to a pull request? Or link back to the deployment summary screen with the results displayed there?
4 votes -
OAuth support for outgoing webhooks
Currently outgoing webhooks support only basic authentication. It'd be useful to have oAuth support for outgoing webhooks for enhanced security.
5 votes -
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).
1 vote -
Add the ability to restrict the Jira Projects Gearset can access
A Jira account may be linked to many projects which will never be interacted with through Gearset. However those projects might still be legitimate for the user, so they can change their project access on the Jira side. It would be great if we could select projects in the connection that we want to choose from when associating to a Jira item.
1 vote -
Ability to merge the pull request from inside gearset. It gives me option to stay in one tool and carry out all my opertions.
In Gearset we have option to raise the pull request but we cant approve merge them inside gearset. There should be a checkbox which if checked should go and merge that pull request. That will allow the user to stay in one screen/one tool i.e. gearset. If someone wants to keep its approval processes in bitbucket then checkbox will allow them to only raise pull request and not auto merge/approve.
4 votes -
Show associated JIRA ticket in Validated Packages & Deployment History and Export
We would like to view the associated JIRA in both the Validated Packages and Deployed History pages. In addition, we would like to export the associated JIRA tickets in the Export History Excel report, found in the Deployment History page.
We link our Jira stories to our Production deployments and we would need a way to report on which ticket is linked to which deployment. Currently this is only available if users are diligent enough to also write the story number in the Friendly Name or Notes.
This would be an extremely useful feature especially for companies undergoing SOX Compliance…
3 votes -
Remember last used repository and branch for Azure DevOps integration
Remember the last used repository and branch in all places.
2 votes -
Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered
Need a Integration of Gearset & Jira , once the user story is updated in Jira , My gearset job will get triggered and deploy the components related to that user story.
and once the deployment is done , update the jira ticket status as deployment done.2 votes -
Select source control based on actual setup/connections when starting comparison
When starting a comparison and selecting source/target environments for Source Control - it shows all connection types including those that I haven't connected.
With browser cache, it seems to remember the one you selected last. However, for new users (or when you clear cache) it'd be ideal if Gearset would default your source control on this screen to whatever the user has connected. Once a user has connected a source, there's no sense in having the user choose it again at this step.
3 votes -
Jira ticket association should carry over to deployment merges and comparison refreshes
If I clone a deployment, it copies all the associated Jira tickets, but if I merge two deployments, the list of associated Jira tickets is empty. Is that how it is supposed to work? I would expect a union of the lists of all the merged deployments.
The same would apply to comparison refreshes.
1 vote -
Jira: Ability to pass a list of Jira ticket Ids vs. single entry
Would really benefit from being able to paste a list of Jira Ids, e.g. comma-delimited (similar to specified tests) on final deployment. Hate giving up validation / deployment status writebacks to Jira, but often we have packages spanning dozens of Jira tickets and entry can be time-consuming, especially if there is a failure or refresh needed and Jira ticket associations get lost from the draft.
1 vote -
Ability to trigger different CI jobs or changing the targets based on the user who did the commit in source control
Related to CI jobs can you set up multiple jobs to trigger based on which user did the commit to source control? The goal would be having the deployment / last modified dates in SF reflect which user did the commit in source control and triggered the CI job.
I don't think that's possible as I don't see any kind of filter or way to manage which CI job should fire when source control is updated so the audit history in SF will only reflect one specific user doing the deployments and people would need to review the details in…
1 vote -
Github: Ability to select Reviewers for pull requests created in Gearset
Currently, you can create a PR after a successful deployment in Gearset. You're able to provide a description and even select it as a draft.
However, the only potentially necessary field that's missing is "reviewers". This means any CI/CD setup you have that requires an approval requires the user to go into Github just to add the reviewer.
Since Gearset would have all the team members (and those with linked github accounts), it seems it might be an opportunity to select based on that list and pass the linked username on to github in the PR creation to keep end…
2 votes
- Don't see your idea?