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
-
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 -
Delay Jira status updates until after post-deployment steps are completed
Currently, when using the Jira integration with Gearset pipelines, status updates happen immediately after the initial deployment completes, but before any post-deployment steps are executed.
We need the ability to configure Jira status updates to occur only after ALL post-deployment steps are successfully completed. This would ensure tickets only show as ready for validation when they're truly ready to be tested.
This is important for teams that have mandatory post-deployment steps (like data imports, configuration changes, or additional verifications) that must be completed before a story is actually ready for testing. The current behavior can lead to confusion when testers…
4 votes -
Add an option to ignore ".forceignore" files
When a repository contains a forceignore file, deployments to that repo will not include these elements.
Sometime however it might be necessary to explicitly deploy these elements (e.g. manually).I propose to add a flag "Ignore .forceignore" at least for manual comparisons + deploys to be able to still push generelly ignore components to the repository.
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
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 -
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 -
Post pull request descriptions to linked Jira ticket
It would be good to have the ability to post pull request descriptions to the linked Jira ticket of a feature. Currently there is limited visibility of the pull request description as its only visible in the code repository, therefore it would be good to see it on the jira ticket as a comment.
1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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.
7 votes
- Don't see your idea?