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.
1179 results found
-
Precision Deployments for Lightning Web Components
It is very much required to have Precision Deployment for LWC components as it is common to have multiple developers working on same LWC
1 vote -
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 -
Notifications for the errors in the webhook page on Pipelines page
Add possible to configure notifications for the errors in the webhook in the Pipeline. Similar to CI Job notification. Ideally post to Slack
1 vote -
Compare Types on Comparison
For the pipelines observed when creating a feature branch and during comparison runs, a default filter is applied to the compared types without any metadata types selected (0). We would like to have a custom filter with metadata types for a specific pipeline pre-selected by default when the feature branch initiates the comparison.
3 votes -
Query for Deleted Records
It would be helpful to have a way to query for all deleted records across multiple backup jobs for a specific object.
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.1 vote -
Allow tests to be run in parellel in multi orgs and allow aggregations of results for PR validation and speed up non prod deployments
We get 100 sandboxes, Can create test orgs org1, org2, org3 where our unit tests are split and run in them so hour long tests just take 1/3 the time? We would like it to be part of our pipelines as of now PR validation to develop takes 40 mins which makes it unustainable.
1 vote -
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.
2 votes -
Help to have a change log, including the name and email of the person who changed the test level in CI jobs?
The test class level change in the job is crucial for us; if someone changes the test level to no test in place of a specific test run, components will go without a test run.
So, if we monitor things on a regular basis, we can ensure that everything is in place.
If we have a tab to get all these kinds of information, such as reports1 vote -
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.1 vote -
Gitlab Self Managed Issues
We suspect that reading the 'weburl' response field for the specified branch from an API call to GET 'v4/projects/$projectid/repository/branches' might be causing a problem when using public Gitlab proxies.
We suggest implementing a code change to compare the domain of 'web_url' to the self-hosted GitLab domain provided by the customers. The customer's self-hosted GitLab domain should take precedence.
1 vote -
Set up notification according to the target connection we're deploying to.
Set up notification according to the target connection we're deploying to. This way, the scheduled and manual deploys will notify us with what we set up.
1 vote -
Conflicts between the Feature branch and Promotion branch as comments in the Github PR.
Currently when there is a conflict between the feature branch and the promotion branch in Github- The Gearset Github app does not move new commits to the promotion branch. This totally makes sense but it is not obvious to a developer what is going on. I suggest that the Gearset app post a comment to the PR (or a message in the Github Check run maybe) that there is a conflict that needs to be resolved before new commits to the feature branch will propagate to the associated promo branches. Thanks!
1 vote -
Allow deployment of 'Check For Matching Records' in Flows.
As part of the new Salesforce Summer ’24 release, Salesforce have added the ability to check for matching records when using a ‘Create Records’ element. We’ve used this useful feature in various locations within our new flows to identify existing contacts for example.
When deploying the flows using this feature between developer environments via Pipelines or Compare & Deploy in Gearset, we’ve noticed that this new setting within the element doesn’t get deployed and is switched off in the destination org.
In the meantime, we can manually turn on this feature in the destination org.
1 vote -
Add the "cloned from" friendly name somewhere on the comparison page.
This suggestion is specific to comparisons that are initiated by cloning a package (that already has been named). Gearset / salesforce takes a bit of time to finish its comparison/validation, so often times I'll open up to 5+ tabs one for each of my gearset deployments. As the comparisons complete, I'll move between the tabs to progress through the steps, but as you can imagine it gets confusing which compare is cloned from which deployment.
Possible ways to display on UI:
When cloning a single package -
e.g.
Apps-87431When multiple packages are combined -
e.g.
Apps-87431
Apps-87431-Step2
Apps-87431-AddFieldUsually,…
1 vote -
Save sort order in Saved comparison pairs
It would be nice that the chosen sort order of the saved comparison pairs could be saved.
If I choose to sort the saved comparison pairs on Friendly name and i open a new tab of gearset, the saved comparison pairs in the new tab are sorted on last used. It would be nice that in the new tab, the saved comparison pairs are sorted based on the same column as the previous tab.1 vote -
Add an option to ignore API version differences during comparisons
When comparing Apex, and other files with API versions the difference engine will mark any files with higher API version as "changed", even if the API version is the only change. This can be undesirable when there have been bulk updates to the API version that have not been made in the development environments. It would be great if the comparison engine could make it clearer when the only difference between two files is an API version (especially when the target is on a higher API version)
1 vote -
Split Lightning Page Metadata Type
Think the Lightning Page metadata type needs to be split into 2 categories. Reason being it is the one metadata type that causes comparisons to run for extremely long times or even crash/time out. This happens because it trying to compare all of the lightning email templates users make. It would be better if lightning email templates were their own metadata type and the lightning page type was actually just lightning pages created for objects.
1 vote -
Allow open PRs to queue up.
Allow open PRs to promote via selection and to queue up against the target keeping blocking behaviour to just merges and the deploy activity
1 vote -
3 votes
- Don't see your idea?