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.
1240 results found
-
Avoid manual selection of component while compare and deploy
Good to have options in Gearset to auto select changed metadata files(changed as a part of pull request) while doing Compare and deploy.
Imagine one pull request number 5377 (which is changing 200 metadata files moved from 1 branch to another branch).
Now while doing compare and deploy It is good to have options which auto select this 200 metadata for comparison. This can help me from this manual selection of 200 metadata files which is very time consuming.1 vote -
allow users to customize Slack notifications
It would be great to have some ability to customize the notifications, specifically:
- change sender/title. right now it just shows up as my name.
- add a link to the monitoring history to allow wasy one-click into monitoring reports to see what specifically has changed.1 vote -
Keep the same record owner between source and destination orgs.
Alternatively, allow the change of record owner before importing data to destination org.
1 vote -
add files to a gitignore during Suggested Fixes
When I make a comparison, Gearset will helpfully check the deployment and offer suggestioned fixes, such as... exclude object components belong to managed packages. now, i can agree to that solution and exclude those files, the problem is they persist every time i make a comparison, they always show up as changes. Would it make sense to be able to add them to a list of ignored changes?
1 vote -
Exclude the subcomponents of the parent Workflow metadata and also exclude list views from custom objects
I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments
1 vote -
Option to choose CI validation run behavior with Open Pull Requests and Branch updates
Currently, if you have a CI job set up to validate based on events (push, pull request) on a specific branch the following occurs:
You open a pull request against the specific branch noted in the job - CI validation runs
You push a commit to the source branch of the same open PR - CI validation runs
You push a commit to the target branch of the same open PR - no validation runsIn the conversation with Dan on 8/13/2020, I was told this is by design on Gearset's end (to ignore that situation) to avoid long queued…
1 vote -
Only show JIRA tickets with specific statuses
We would like to the ability to only display JIRA tickets with specific statuses (e.g. Approved, In Progress).
1 vote -
Deploy Einstein Datasets from one org to the other
Copying of Salesforce objects with relations is a great feature. But this does not support Einstein datasets to be copied from one org to the other. It is critical for teams to have Einstein dataset in the lower orgs for development and testing
1 vote -
Cloning deployments: add namespace option
If you are using Gearset to develop for a 1GP managed package:
Your deploys between VCS and dev orgs/scratch orgs DON'T use namespace in the metadata filter
Your deploy from VCS to Packaging org MUST USE namespace in the metadata filter - otherwise, everything in the difference viewer appears as NEW rather than CHANGED (if truly just edited during dev cycle)
So, when cloning a deployment, one should have the option to add the namespace to the clone dialog.
Without this, one has to repeat the Compare step thus losing the benefit of what you had enumerated in a prior…
1 vote -
Spurious difference CustomObject excludedstandardbuttons ordering
SFDC has a tendency from release-to-release of reordering the excludedStandardButtons for a CustomObject. If you are using source control populated under Vx and SFDC changes the ordering in Vx+1, your custom objects all show up as Changed in the differences viewer.
Because these are "excluded" buttons, their ordering in the XML file doesn;t matter to the end deployment and the variance should be suppressed in the difference viewer.
1 vote -
Use exact filters of Automated Job
Currently automated CI job filters are unique to that job and not available as a filter for manual jobs.
Ability to use the exact current job filter as a filter outside of the CI job.
Ability to to clone the CI Job filter into a new named filter.1 vote -
no difference report
Currently the deployment report that is attached to the Jira ticket includes all "No Difference" components which I don't believe provides any real value. In my instance, this includes endless amount of pages, from what I can tell the changed values I'm actually looking for don't actually exist. I would suggest either excluding from report all together or providing a summarized statement that is just a grouped item for all items that were included in deployment but had no change. Also the report should bring the actual changed items to the top of the report like it is on the…
1 vote -
Support JWT authorization to DevHubs
If Gearset could authorize the DevHub using a JWT (requires DevHub to have a Connected App and Gearset to be given the clientId + server.key + username) ...
Then:
* Scratch orgs created by Gearset could be accessible to any other machine provided that machine is using the sfdx force:auth:jwt:grant command (same clientId, server.key, test.salesforce.com, and username of scratchOrg)
* This is a prerequisite to any outgoing webhook that wants to auth against the CI scratch org
* This is a convenience feature to IDE users who want to auth against a Gearset-created scratch org without having to get a…1 vote -
Migration/Deployment Path
In cases where you have multiple environments, provide an option to define a migration/deployment path; ability to define what environment is the source and what is the target. This will be useful in cases where we have requirement to deploy changes to say production from a specific environment (UAT).
1 vote -
Workflow failed to deploy without error, due to standard object dependency
In a CI job : Validation shown as success & Deployment shown as success. But actually no workflow deployed due to it being removed in the Problem Analyser.
The Problem Analyser triggered due to the (standard) object, that the workflow depends on, not being in the comparison results.
In a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap - problem analysers should never fire on object dependency.
1 vote -
Workflow failed to deploy without error, due to standard object dependency
CI job : Validation shown as success & Deployment shown as success.. but actually no WF deployed. Saying Opportunity object doesn't exist in target just because it was not selected in the components. in a traditional deployments object is not needed to deploy WF, that too standard object. I feel it is a gap.
1 vote -
Link Static Analysis results to the code
Could we link the file names in the static analysis results to the actual code from the comparison/monitoring job?
i.e. Where the results have a list of issues per Apex class, I'd like the class name to be a link to the code for that class
Having a quick peek at the code from within Gearset can help me to diagnose whether it's a genuine problem, or something where the static analysis rules need tweaking.
If it's just the rules that need tweaking, it would be nice to be able to complete that job entirely within Gearset.
1 vote -
Suppress the <deprecated> tag in CustomObject, CustomField
When retrieving metadata from 1GP packaging orgs, the <deprecated> tag appears in the source and, if you deploy to VCS, is preserved. But if you subsequently deploy to a scratch org, and back to VCS, the deprecated tag no longer appears in the scratch org and thus shows up as a diff in the Difference Viewer - confusing the user.
Doc says this tag is reserved for future use and until such time as it is used, suppress
1 vote -
Tie scratch org URL to enumerated list of scratch orgs on My Connections
UX suggestion (tie list of scratch orgs to URL)
If you use Gearset to create a scratch org, the list of scratch orgs on the My Connections page does not tie to the visible URL of the scratch org you log into
This gets to be a real issue for the multi-tasker who might have several scratch org tabs open at once but has no way of knowing which one is which vis-a-vis the Gearset enumeration of how the scratch org was logged into the first place. Drilling into the user's name is too clunky
1 vote -
Move the configured regex filters to the top of the scrollable pane (currently at bottom) of
Move the regexes to the top of the pane so one can see they exist and not have to guess that they exist at the bottom of the pane.
Note the example, selects all custom objects - this is useful for ISVs
example: For custom object, there are 100+ entries for standard and custom objects. If you add a regex, it appears at the bottom of the scrollable pane, after all the enumerated objectnames. Coming back into a custom filter, it is not obvious that you had even created a regex as you would have to know to scroll to…
1 vote
- Don't see your idea?