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.
1140 results found
-
Build Comparison Manifest from pull request
It would be cool if the custom deployment configuration could be driven from a Pull Request . For example, in GitHub, the Pull Request knows which files were changed and approved. Why not use that list to instantly populate a comparison to create a deployable manifest to go from source control to org?
15 votes -
Write Deployment Results back to the user's Salesforce org
When setting up a deployment, it would be helpful to capture Deployment Results in a custom object in the running user's Salesforce org. Users would be able to specify a unique reference at the point of deployment, which would track through to the Salesforce org.
Information about the deployment would be captured in a Master record, with data about individual components existing in Detail records.
Org admins would then be free to leverage automation features to map the created records as they see fit.
As a consultancy that tracks our customer requirements in Salesforce, our use case would be that…
14 votes -
Deploying Profiles - Create, Update, Delete
I have noticed that in some scenarios, user profiles cannot be created, deleted or updated. In addition, some pieces such as user license cannot be updated due to the Salesforce architecture. To create a new profile with a specific license, we would have to clone an existing profile that has the correct license and then update the permissions accordingly. When deleting a profile, first we need to ensure that the profile is not associated with a user (it doesn't matter whether the user is active or inactive) and then the profile can be deleted. When updating a profile, based on…
14 votes -
Jira comment only for production releases
We would like to have the option to choose which deployments create Jira comments. As business users often watch our Jira tickets, we would prefer only posting comments when we actually "release" (deploy to our production org) and skip comments for releases on sandbox environments.
13 votes -
Delta only validation CI jobs
Idea is to have the Delta CI for Validation only Job, so the as well, so the validation process will become faster .
The option of validating a PR in the deployment job does the same task, but is comparing too many items of metadata and it is taking too long.
13 votes -
Set fields to a specific value during a data deployment
When deploying Data, it would be nice to be able to set field values. It could be just to null them or set a value. It could be part of the configuration or data masking.
13 votes -
When validation fails, allow option to automatically remove metadata from deployment that was causing failure
It's not convenient when a validation fails, to then download the excel file of the the validation errors, view in separately form Gearset, and then go through the list of metadata I'm trying to deploy and try to uncheck each one that failed the validation. It would be nice if Gearset did that for me.
13 votes -
Allow date range filtering on the "Changed On" column
Currently one has to pick dates individually, if one has 30 + dates to select, this can be massively simplified if one could select a date range.
13 votes -
Allow CI deployment notifications to the specific user who made the source control commit that prompted the deployment
We have CI jobs that fire on commits to a source control repository. At the moment, there is no way to email the specific individual who made the commit that prompted the deployment, so we have to notify everyone involved in the project whenever a deployment fails. If we could just notify the individual who made the commit (plus the deployment manager), it would reduce noise considerably.
Please add this feature.
13 votes -
Ignore Unlocked Package Metadata In Comparisons
Currently, metadata from Unlocked Packages show up when comparing against an org. This leads to duplication of metadata in source control repositories (correct DX package repository and incorrect monolithic, "happy-soup" repository).
Using the Package2Member Object (Tooling API), it is possible to deduce whether or not a metadata item is part of an unlocked package. Therefore, it should be possible to ignore some or all unlocked packages (or any Package2 package), in a similar fashion to the way Gearset filters allow inclusion or exclusion of managed packages.
13 votes -
Allow deployment of Sharing Rules by Rule not by Object
In change sets we can pick individual sharing rules to push (specific ones on an object). However through gearset we can only push the whole object.
13 votes -
Make Custom Filters a Top-Level Menu Item
Filters are arguably the best part of gearset, especially with the support for RegEx. It is kind of a bummer that they are tucked away in a modal that can only be reached by clicking into a dropdown. Ideally you could just go to Hamburger > Metadata Deployments > Custom Filters and be routed to a dedicated page.
12 votes -
Make "Hide Reodering" global switch
Please add a feature to have globally selected "Hide Reordering" and also hide those files that have no changes after reordering from Changed Items?
Clicking that on every file to see that there are no real differences is time consuming and slow down the comparison process.
Scenario:
1. I am comparing two sandboxes develop with my private sandbox to align with changes made on develop.
2. I have comparison with many Global Value Sets, Custom fields which are Picklists, flows etc.
3. Most of them are not changed but are listed as changes. I need to click on each metadata…12 votes -
Ability to search Deployment History for specific metadata
On the "Deployment History" tab, the filter dialog filters on the visible friendly name and items like that. What I would like to do is enter a specific metadata name and have the list filter down to deployments where that specific metadata name was a part of the deployment. This would be useful when getting the question, "when was xyz last deployed?"
12 votesIf we implemented this and it was only able to search metadata from that point in time onwards, would that be useful or would it be confusing to communicate in the UI?
-
Adding Custom destructive
ANT is unable to change the type on an EmailTemplate from HTML to CUSTOM. To solve that we need to add the EmailTemplate first to the destructive package to have it removed and then add it again with the package.xml
Since this file is not deleted but just changed. It doesn't show up in the deleted items tab.We should add an option to the "Selected Items"/"Changed Items" list to opt-in for adding that to the destructive.
12 votes -
For CI Jobs initiated by Github, dynamically send CI failure / success email to the user who committed to the repo.
Currently, we can only specify a list of users to email, a Slack channel to update, or a Chatter group to post to when a CI job is successful or fails. If there are multiple notifications to a number of people, it's likely they will filter out these messages, so being able to notify the person who the CI Job is most relevant to would be a good improvement.
12 votes -
Allow deployment of PROFILE only
The main reason we considered Gearset was issues with deploying profiles. Half the object settings, if not more, don't come over with change sets. When attempting to use Gearset to ONLY deploy a profile, we had the same issue. So, what's the point of using GS then? When I talked with one of your technical resources he did mention that was not a common use case. I would think it would be for large organizations like ours (over 3500 employees). We may want to spin up a new profile and just deploy that with no app or any other features…
12 votes -
When the difference between Source and Target, on a particular line, is only in the formatting. Highlight in a different color
From what I can determine you are categorizing the differences as follows:
Code in Source, not in Target – Highlighted in Green
Code in Target not in Source – Highlighted in Red
Difference between code in Source and Target – Highlighted in YellowWhen the difference between Source and Target, on a particular line, is only in the formatting. It would be nice if that was highlighted in a different color than yellow (perhaps grey). It would speed up the review of the code knowing a certain color was only a formatting difference.
12 votes -
Hide re-ordering in a Monitoring job
We have a monitoring job set up to check production changes. However, re-ordering in some components are popping up as false positive. For example, Entitlement Process and Site.com. Everyday I get an email saying # of changes have been made on production. I'd like to not see these false positives in the # so that I do not need to go to each comparison every day just to realize that it's a re-ordering issue.
11 votes -
Ability to specify test suites when deploying apex classes. It would be easier when there are a large # of test classes involved.
Ability to specify test suites when deploying/validating apex classes. It would be easier when there are a large # of test classes involved with a deployment
11 votes
- Don't see your idea?