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.
158 results found
-
Provide integration with WebexTeams
We moved from Slack to WebexTeams and have lost the ability to post deployment notifications from Gearset. Here's an article about Webex Bots: https://developer.webex.com/docs/bots.
3 votes -
Allow sfdx project files for scratch org creation
When creating a scratch org, allow us to select/configure a sfdx-project.json. This will allow for more complicated sfdx project to be deployed, i.e. multiple project folders, namespaces, ... etc.
3 votes -
Eliminate unnecessary XML reformatting in git
Currently, when gearset deploys XML to git, it seems to run it through a reformatter, which creates superfluous changes in git. These changes cause extremely large deltas, which are hard to read, increase the difficulty of merges and the likelihood of conflicts, and make working with any other metadata tooling (like SFDX) difficult.
For example, here is part of a delta gearset commited for a profile.xml:
diff --git a/force-app/main/default/profiles/Commissions.profile-meta.xml b/force-app/main/default/profiles/Commissions.profile-meta.xml
index 8b11e6b7..3d640a50 100644
--- a/force-app/main/default/profiles/Commissions.profile-meta.xml
+++ b/force-app/main/default/profiles/Commissions.profile-meta.xml
@@ -1,10 +1,27 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
+<?xml version="1.0" encoding="utf-8"?><Profile xmlns="http://soap.sforce.com/2006/04/metadata">
+ <custom>true</custom>
+ <profileActionOverrides>
+ <actionName>Tab</actionName>Note that it lowercased…
3 votes -
3 votes
-
Add an integration for Google Chat that includes an integration for Change Monitoring and Unit Testing.
Recently, it seems that Google Chat has reached some feature parity with Slack in that it has a defined integration avenue for adding notifications to Google Chat. I have found that I can set up a custom webhook to Google Chat for the CI jobs, but webhooks are not available on the other 2 features I am looking for notifications from.
I would either like to have:
a.) An integration for Google Chat with an app on the Google Chat side that we would add for the connection to our Gearset
b.) Webhook availability for more notifications, so I can…2 votes -
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 -
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.
2 votes -
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 -
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 -
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 -
Pipeline PR User interface Details
Currently we can see Jira ticket status when we look at PRs in the pipeline UI it would be phenomenal if we could include additional Jira fields to be seen from Pipeline UI such as Summary or fixversion
2 votes -
Allow a PR template from GitHub to pre-populate the PR description
There is a feature in GitHub to auto-populate the PR description (forcing, for example, a checklist if using the web UI). If Gearset could read that template and pre-populate the PR description so users have to put in specific comments (such as manual steps to be done after deployment) and if that description were exposed in GitHub, then it would be more seamless and the deployment history would enable an admin to work through each manual step without looking in closed PRs in Gearset.
2 votes -
Allow squash merge for Github PR
We have our GitHub PR settings set to only allow Squash and Merge for PRs because we want a clean history on the long-lived branches. It seems Gearset doesn't support this, when I attempt to promote it issues an error. This should be configurable or should detect this automatically from the settings.
2 votes -
Have the Jira ticket which was selected at the point of the commit stay with the PR in Pipelines
At the moment when you select a Jira ticket at the point of commiting to a branch, you are able to track that actionback into Jira.
However when a PR is opened from that feature branch to the next environment branch (in the Pipelines UI specifically) the Jira ticket association is lost, and has to be reattached manually.
Workaround:
- Put the ticket ID in the branch name, i.e. name your branch "feature/AL-99- new-flow"
- Use the drop down menu provided in the Pipelines UI to re select the Jira ticket
- Open the PR from the Commit successful screen and tick the…
2 votes -
Have the Jira ticket which was selected at the point of the commit stay with the PR in Pipelines
At the moment when you select a Jira ticket at the point of commiting to a branch, you are able to track that actionback into Jira.
However when a PR is opened from that feature branch to the next environment branch (in the Pipelines UI specifically) the Jira ticket association is lost, and has to be reattached manually.
Workarounds:
1. Manually add the ticket ID to the PR description, which will reassociate it
2. Use the drop down menu provided in the Pipelines UI to re select the Jira ticket
3. Open the PR from the Commit successful screen…2 votes -
Disable Jira notifications for individual CI Jobs
We like that the Jira integration posts changes to the associated Jira ticket during a deployment, but we only want notifications for specific CI Jobs. For example we want our staging and prod deployments to post a notification in our Jira ticket, but not for other jobs such as back-deployments. Each post potentially emails Jira users and we want to limit these notifications. Currently the only work around is to remove the Jira ticket association from the PR in Gearset before promoting it, and this gets tedious if you have a lot of development orgs.
2 votes -
BitBucket commit on a successful Org deployment
It would be a nice feature to have a setting on the deployment summary page to also commit to a git branch with deploying to an org.
2 votes -
Exclude OmniStudio generated LWCs for CI
Currently OmniStudio will generate LWCs for it's flexicards and OmniScripts.
We want to have CI syncing in to a repository, however we don't want to have these autogenerated LWCs in the repository. This is code that users won't be modifying themselves, isn't constructed to be read by a human, and will actually be controlled by the Vlocity elements that GearSet already supports.
Reviewing the metadata produced by omnistudio, it seems that all the LWCs produced have the runtimeNamespace tag in their meta.xml file set to 'omnistudio'. It would be ideal if we could filter out all LWCs with that tag/value…
2 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 -
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
- Don't see your idea?