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.
1308 results found
-
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
Problem Analyzer should remove picklist values from record types when picklist values are removed from the picklist or value set.
When removing or deactivating a picklist value, Problem Analyzer should remove these values from any record types that reference them. While the initial deployment of the picklist may succeed, subsequent deployments of the referencing record types will fail if they still reference a deactivated picklist value.
1 vote -
Picklist Comparison should show if value is active/inactive
When comparing a picklist in which we have deactivated values, the simplified comparison visualization shows the deactivated values as being "added" (in green, on the source side).
The XML reveals <isactive>false</isactive> is being added, but the simplified view seems to suggest new values are added instead
1 vote -
New, one-click "Promote" button is very risky
In Deployment Pipelines when a PR for a CI Job is selected, a new, one-click "Promote" button exists, if the PR passes merge-conflict and validation checks. This new button is very risky in that it begins the promotion process, without recourse, when clicked.
Perhaps that's the designers intent but for myself at least, the button is too easy to accidentally click out of inattention, distraction or mouse clumsiness and is especially risky in that I cannot recall the action.
Personally I like the process of clicking the PR checkbox and clicking "Promote", which prevents unintended deployments.
As an alternative to…
1 vote -
audit report missing PR message
The audit reports don't include much context of the deployment, which means they are pretty useless to us and do not serve our auditors' needs. Specifically, they do not include the PR message for deployments through our pipeline, which means we can't link each deployment to the specific ticket responsible for that deployment. The PR message is where we put our ticket. This information is needed for our SOX audit process. Additionally, we can not see a link back to the deployment, which would allow us to quickly reference the specific metadata files/components that were deployed.
1 vote -
Pre-fill Pull Request Description with comments from last commits
In order to save time, when a Pull Request is created from the Pipeline, the Description field could be pre-filled with the comments from the last commits in the feature branch, instead of forcing the User to type something.
1 vote -
Use location of metadata in source branch or local folder when adding to target branch
When adding a file from a branch or local folder (source) to another branch (target) not having the file, use its location in the source as the location in the target.
Currently all new files are placed in the default folder [1].
Let's assume a new file, "HelloWorld.cls", in the source is located in .../force-app/main/default/classes/special/ and that class doesn't exist in the target. When the deployment is complete the file should exist in the target's .../force-app/main/default/classes/special/ folder, matching its location in the source. Currently it would be placed in .../force-app/main/default/classes/.
[1] https://docs.gearset.com/en/articles/2835001-structuring-your-source-control-repository
1 vote -
Save sort order of grids
It would be nice to be able to sort by column names and save that sort order for the next time the page loads or save a default sort order. We sort often by jobname and would like to not have to resort everytime we need to touch a ci job to sort the column.
1 vote -
Add support for CMS Collections
Please add support for CMS Collections in the comparison filters as well as the deployments and CI jobs.
We're working with CMS Collections in our current developments of a customer community and we'd like to deploy this metadata as well.1 vote -
is it possible to add a filter for "selected feature branches only" ?
is it possible to add a filter for "selected feature branches only" ? My business problem is that i am a deployment manager and i need to quickly validate what ive selected before building the release.
1 vote -
Is it possible to get an additional field in the compact view of the jira ticket ?
Is it possible to get an additional field in the compact view of the Jira ticket ? We would like to add Fix Version as well as what already exists.
1 vote -
Show Date/Time of Validation Run in Validation Details
I would like to see the "Effective Date" of a validation in the Validation Details screen (at /continuous-integration-job-validation-errors).
I only ever access this information from the Deployment pipelines and so don't ever see the date/time the validation was run (near as I can tell this is only available in the CI jobs section).
To better explain my reason for asking:
Oftentimes when a validation fails it is sufficient to rerun the validation (on account of Delta CI jobs doing weird things sometimes). What I've found myself doing is perusing the validation errors, clicking "retry validation", then going about other tasks…1 vote
- Don't see your idea?