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.
1142 results found
-
backup expiration
For compliance purposes I'd like to request an option to list the data backup expiration date. We are able to choose how long to retain the backup, but I do not see a place that lists when the backup is set to expire.
4 votes -
Allow Quick Deploy when merging multiple PRs using Pipelines
currently when merging multiple prs using pipelines the merged package validates and then the prs are merged, the resulting deployment then revalidates even though quick deploy is an option, can we use quick deploy when available like was enabled in the ci jobs?
this would save time by avoiding double validation and make the feature more usefull.
2 votes -
Validation job when PRs are raised
Requirement :
Provide option to create a CI Validation Job only with "Validate pull requests targeting the source branch" and keep "Run Job" dropdown as optional .As Of Now :
When we raise a PR, it initiates feature branch validation ( cos, we enabled "Validate pull requests targeting the source branch" ), and after that when we merge feature-branch to target branch, it re-initiates another validation job.
For us, it's like similar validation is running twice on different events from which we can't opt out.Pros :
We can handle when to validate a feature branch, instead of bundling…
1 vote -
Consolidated Reporting for CI Jobs
Hello. One item we struggle with is keeping track of CI Deployments that didn't fail, but didn't deploy as expected. The two causes we usually see are:
1) Something was removed by problem analyzer
2) We deployed something that Salesforce says succeeded, but no changes were made (e.g. deletion of picklist choices)We currently have about 100 CI jobs which makes it impractical to go into each one.
The proposed format would look like a csv export:
Job Name, Date, # Created, # Updated, # Deleted, # fixed by problem analyzer
Opening a CI job history looks fine, but we'd…
1 vote -
Add the option to schedule weekly, monthly and yearly backups
To meet our backup compliance requirements I'd like to suggest an option to schedule weekly, monthly, and yearly backups to go along with the daily backup option that is currently available. This way, we could setup multiple backup tasks with different retention.
Thanks
5 votes -
When Problem Analyzer adds Fields, Add Profile Permissions Too
Currently the problem analyzer will identify missing fields. However, it doesn't prompt or allow you to add the permissions for the fields. So, you either have to go back, manually add all fields as Selected, or push the package and then go back manually and add permissions for all fields. It should prompt to add both the fields and the permissions.
2 votes -
Analyzer: Duplicate child relationship name detection
Use case -
target org has child object O lookup field F1 with childRelationship = Foo
source org has child object O lookup field F2 with childRelationship = FooIf you deploy, SFDC tells you that there is already a Child Relationship Foo on O
Analyzer could detect this and warn developer before deployment
3 votes -
Analyzer enhancement - detect missing ContentAsset in CustomApplication
Given this XML in CustomApplication
<CustomApplication xmlns="http://soap.sforce.com/2006/04/metadata">
<brand>
<headerColor>#0070D2</headerColor>
<logo>MyLogo</logo>
<logoVersion>1</logoVersion>
<shouldOverrideOrgTheme>false</shouldOverrideOrgTheme>
</brand>If user forgets to select Content Asset MyLogo, Analyzer should detect.
3 votes -
Automate creation of a release, which includes several stories
Within pipelines, provide the ability to validate multiple Pull Requests (PRs) in one shot (i.e. release), so that this release could be deployed to production, for example, using Salesforce's Quick Deploy feature. This would be very handy when getting ready for a production release and I need to validate my release the day before. Thus, on the day of the release, I would simply Quick Deploy it.
3 votes -
Provide account owners ability to control and lock certain features for team
Currently, there are some settings that we would like to turn on or off for the entire team. For example, the "Append Validation/Deployment items to ticket" toggles when doing a deployment. It is also unclear that when a team member changes these, they are changing the setting for the entire team, which leads to inconsistent Jira tickets, as some list the components and some do not.
We would like the ability for account owners to control these settings for the team and lock their ability to be changed by team members.
4 votes -
Copy reviewers to the cloned promotion branch PR in Pipelines (Bitbucket)
When Pipelines creates a promotion branch and copies a PR that was opened in Bitbucket, it does not copy the reviewers. This means reviewers have no way in the Bitbucket UI to filter for PRs that they're assigned to review.
Further, since all the cloned PRs are authored by the Pipeline owner, the lack of reviewers on top of that makes it quite difficult to visually differentiate between the list of open PRs, especially if you're both someone who creates & reviews PRs.
3 votes -
Provide More Detailed Information on Data Deployment Summary Steps
Currently the data deployment summary displays an elaborate interface but with very little useful information other than record counts. On the right side are Steps, but those steps do not tell the user much. I can see that in one step x records were fetched, for example, and in another step y records were fetched, but I can't see WHY.
Example use case: I had a situation where I was filtering an object but the filter wasn't being honored (more records were being deployed than expected). I could see from the data deployment summary that one of the steps was…
1 vote -
Add issues from the problem analyzer to the comparison list
When I find issues in the problem analyzer, if I accept them, they only add the things that I have selected, but I can't add any related elements without going back to the comparison.
For example, if I miss a custom field in the comparison, but the problem analyzer flags it, I don't have any way to add the permissions for that field.
Instead, I have to go back to the comparison and add that missed field and then it's related features (this is a big problem if the analyzer flags a number of issues).
Having a button in the…
4 votes -
Filter on UNselected items when choosing metadata to compare
When selecting metadata to compare, there is a picklist that says "Filters" and has an option for "Selected Only." Please add a second option for "Unselected Only" so I can quickly verify that I haven't left anything out without my eyes being distracted by checkboxes and items I know I already selected.
2 votes -
Ability to Filter Out Namespaced Metadata
I figured the best way to write this out was in the form of some sub-par user stories.
As a Salesforce Admin, I need the ability to do a comparison of two orgs/repos and have it show only non-namespaced metadata so that I can easily distinguish between things I own and manage vs what are from managed packages.
As a salesforce Admin, I want to be able to indicate that I want to hide all namespaced metadata while still being able to show custom fields I create on a namespaced object so that I can quickly deploy new custom fields.
…
3 votes -
Cleanup Layout Assignments
When you rename a Layout, the previous Layout Assignment won't be cleaned up on the Profile.
This should be cleaned by the Repo dependency cleaner.8 votes -
Add a way so we can easily integrate commits into Salesforce.
What I mean by this is, give users the ability to create and associate commits from in Gearset to a custom Object in Salesforce.
The commit would create a new record in Salesforce, under the custom object, let's call it 'Commits'.
We'd be able to pass through data such as the commit status, the ID of the commit, a link to the commit itself taking us back to Gearset, the name, and author, etc, etc...
I'd imagine this is possible through the use of the BitBucket API, however with SF teams who lack developer resources, this would be a nice…
1 vote -
Flexible Org Monitoring Notification Scheduling
I'd love to schedule a weekly or bi-monthly digest email rather than receiving emails for each run or each change. There are developers who need to know when changes are made, but they do not need to monitor changes frequently. In those scenarios, it would be nice to schedule out a weekly review of all changes.
2 votes -
Multiple metadata comparison filter selection
Having multiple comparison filters to target specific metadata is handy but sometimes you need some additional components for a deployment (e.g Flow & Custom Fields).
The ability to select more than one metadata comparison filter would be a great help and would save on the number of custom filters created and shared.
4 votes -
Allow Filters to be Customised in Pipelines UI
Currently, you can create new filters in Compare & Deploy, but when you are comparing and deploying from within the Pipelines UI on your development org, you can only select existing ones. This either means you have to get your team to go into standard Compare & Deploy to set up specific filters first, or they always have to select the filter that includes everything.
1 vote
- Don't see your idea?