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.
32 results found
-
Stamp Deployment Results with Salesforce Id of the Deployment package for auditabilityq
When a deployment is successful, the deployment results/report should include the Id of the deployment package from Salesforce. This would create a foolproof audit trail between Gearset deployments and when they went into effect in Salesforce.
3 votes -
Add the open PR feature (Github) to work with BitBucket after a successful commit
It would be great to add the open PR feature (Github) to work with BitBucket after a successful commit.
Super helpful for the admin team to close off their feature branches and move onto the next job at hand without having to interact with BitBucket.
2 votes -
Remember default Bitbucket Server repo
According to https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/17292778-remember-a-default-github-repo, when one uses GitHub as a git provider, Gearset will remember the last used repo in a comparison.
However, this is not the case with the Bitbucket Server integration. Every time I do a comparison, I have to select the repository and branch again. With a large number of each, this is very tedious.
Please remember the last-used repo as a default, and do the same for the last used branch on that repo.
1 vote -
Integrate Gearset with Bamboo
Would be important to be able to integrate Gearset with an existing CI Tool like Bamboo, Jankins. (e.g an Bamboo Action or a generic Rest API which can be used by Bamboo or other 3rd party apps)
3 votesThis is now possible since we have released our API, which is available to everyone with an Enterprise license! Please see https://docs.gearset.com/en/articles/6099550-getting-started-with-the-gearset-api for more details. If anyone has feedback or suggestions, please contact us via the in-app widget.
-
Support more than one Dev Hub (sfdx) per Gearset Account | Manage Orgs
The Manage Orgs tabs only allows one to have at most one Dev Hub. This can be limiting in the following use cases:
Your Gearset user account is associated to a PROD org that has Dev Hub enabled yet the Gearset user wants to experiment with sfdx and Gearset using the SFDC Trailhead-recommended 30 day Dev Hub Trial Org
You are a consultant working with multiple clients, each using SFDX and hence each with their own Dev Hub. Yet as consultant, you have only a single Gearset account.
3 votes -
Offer source branch update as option to trigger CI from custom Git (Gitlab in my case)
Please allow to select "when source branch updated" option in the CI jobs section when the source is a custom git repo
2 votes -
Upload Manifest File When Creating Scratch Org
When spinning up a SalesforceDX scratch org, allow a manifest file to be included. One use case is for when the Dev Hub org has PersonAccounts enabled and that feature can be enables upon creation of the scratch org.
2 votes -
Clickable Jira Request within Deployment Report
I would like the ability within the deployment report to make the jira tickets clickable. That way a user could simply click the ticket reference to navigate directly to the request.
1 voteThe Gearset has made this feature available for Jira tickets and Azure DevOps work items, thank you for your suggestion.
-
Gearset integration with Jira hosted on local Server
It will be great to have Gearset integration with Jira hosted on local Server. Currently, we have only with JIRA cloud.
Thanks5 votesSupport for on premise Jira was added in January 2018.
-
Improve formatting of the XML pushed to git
Is it possible to improve the formatting of the XML?
The XML returned from MavensMate is formatted better.It's mainly just missing new-lines.
2 votesWe’ve made a bunch of improvements to the XML formatting this year, including tidying up which namespaces are included and having more consistent indentation and newline behaviour.
As always, we love feedback on the changes we’re making so please submit another idea if there is still improvements we can make in this area!
Thanks,
Kevin -
Allow user to choose the folder in a git repo that contains metadata
Improve git access by allowing the user to define folder where metadata is stored in a git repo.
We are not keeping directly content of src in git branch but src folder because we have there also few other folders.
The problem is that if I try to compare sandbox with git then I am getting results that all files are new.
2 votesThat’s great!
I’m glad that the issue was resolved for you with the adjustment in the location of the package.xml.
Regards,
Stephen
-
Support auto-complete in the dropdown for Source Control repos
Would it be possible to provide an autocomplete dropdown when selecting the git-repo? Similar to selecting the Salesforce-org.
2 votes
- Don't see your idea?