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.
1139 results found
-
Improve comparison performance
If there is one thing that is :-( about Gearset is that for moderate size orgs (a few thousand objects), the default 64 comparison takes too long.
You want to initiate a deployment from source to target and, for whatever reason, you want to make sure you didn't miss anything that needs to be deployed
So, to be safe, you initiate the 64 default comparison.
And you wait (downloading, comparison). This can take several minutes. You go on to other tasks and your zeal to get the deployment done went off onto other things as the comparison time is too…
4 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 -
Initiate comparison from package.xml
I'd like to be able to drop a package.xml file on the New comparison screen. Doing that will have two effects.
First off, it will drive the selection of which metadata types to include in the comparison.
Secondly, it will automatically select the components listed in the package.xml on the comparison results page.
This provides a really good way to expediting a deployment, since package.xml are used pretty universally by both IDEs and standard deployment tools (including packages).It also helps me take advantage of the intelligence of automatic dependency and all of the other goodies that Gearset has. Basically I…
19 votes -
Expand the user security model to restrict user compare / deployment access to defined comparison filters
Hi guys -
In many instances, we would like to restrict user access to certain compare / deploy metadata filters. In our case, it would be rare that all metadata changes are to be deployed and we would like to give our engineers access to only certain filters. This would reduce the risk that items that should not be deployed at a high level will not be deployed. In the current model, if a user has deploy access, they can deploy anything and everything. This is what we are looking to avoid.
Thanks in advance for your time!
Best,
Richard
4 votes -
Save previously entered comparison filters
I am currently using a standard regex filter each time I do a comparison. It has become quite lengthy such that I can't easily remember it. I have ended up saving it in a separate text file and have to open it, then copy and paste it into Gearset each time I do a comparison. Pretty cumbersome.
It would be nice if the Filter... text box on the comparison results screen was a combo box that when clicked, dropped down a list of recently used filters. Each entry in the list should be removable (like with a little 'x' icon…
7 votes -
Have a timer on the compare page to indicate how long the compare is taking
Sometimes a compare can take us 30-45 minutes depending on the complexity of the org. I would like to see a running timer on this page of how long the compare is taking. I don't expect it to say how long is left, just how long it has taken so far. This will help to highlight if any abnormalities are happening, ie. if it's taking a very long time and is only at the Downloading phase for example.
4 votes -
Provide the option to ignore whitespace differences in Apex
It would be great to have more control over the diff process - particularly to be able to ignore whitespace changes.
If I've made an actual function change to a class, and also auto-indented it, then it would be a lot easier to see the important change if I could hide the whitespace-only changes.
Having the ability to suppress whitespace-only changes on the list of changed objects would be really useful, too.
68 votesThanks for the suggestion.
We have plans to improve the way the diff viewer handles changes and whitespace in the future, though it’s not currently under development.
Thanks,
Jason. -
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 -
Have the option to attach test details to test notification email
When you set up notification options for test monitoring, there should be a checkbox for attaching the detailed test result csv file to the email
2 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 -
Support deleting comparison data
Having the comparison history is a great feature, but it would be very beneficial to be able to delete any data in the system, especially when working with a trial account. Part of testing could include working with test environments that you don't want to persist after going live. Also, peace of mind when ending the trial that your data has been removed.
3 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 -
Cancel deployment in progress
In Salesforce, you can cancel a deployment in progress: Maybe because a test has failed already and you don't want to bother running the rest, or because you forgot some things.
Can we have a cancel button while a deployment is in progress in Gearset? The metadata api seems to support it:
https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_canceldeploy.htm
11 votes -
Provide a way to deploy push topics
We have a push topic that we use but there is currently no easy way to deploy changes between orgs. Would it be possible to do this via Gearset?
2 votes -
I need TeamCity to kick off a deployment within GearSet when all my auditing constraints are met.
We currently have a deployment pipeline for our .net and Rails environments that utilize VersionOne, GitHub, TeamCity and Ansible to deploy changes into AWS.
Due to auditing constraints we would like to use VesrionOne, GitHub and TeamCity to deploy our SF changes.
Does Gearset interact with these tools or must it stand on it's own?2 votes -
Chatter posting to
I think it would be useful if Gearset had the capability to make a chatter post to a specific group or @mention someone.
7 votes -
Provide a way to init a sandbox
It would be nice if there was a quick way of init'ing a new sandbox that matches either what was in source control or an existing sandbox.
Currently, I need to run a comparison between the existing source and the new sandbox and then I can try the deploy, but it would be nice if the compare step was not needed and I could simply say 'overwrite what is in the sandbox with what is in the specified source'
6 votes -
Field Tracking Analyzer message is misleading
If source org includes a new custom field with field history tracking enabled TRUE, the deployment analyzer reports the following when deploying to target org:
'Fields with history tracking enabled cannot be deployed before it is enabled on the object. You should remove these history tracking changes from the deployment'
Specific use case was object OrderItem
Analyzer can clearly detect if field history is enabled on target org object (which it was) - message is spurious.
Analyzer can arguably detect that target org's limit (20) will be exceeded by the deployment of the selected custom fields (which could add/remove field…
1 vote -
Here's the best solution: Be able to quickly select the custom objects and standard object custom fields AND only the related metadata items
Would like to be able to quickly select the custom objects and standard object custom fields AND only the related metadata items to make then function correctly (permissions, layouts, field level security, etc..)
Then we could go back and migrate all the process automation stuff - workflow rules, flows, trigger, etc..
It always starts with the data schema first. We need a quick way to see what is different between two orgs and get that synced first
7 votes -
Include both dates on comparison export
The sheet exported from a comparison currently includes only one date column. It is unclear which org this refers to. It would be great if it included two columns (one per org) so that one didn't have to individually look up the item to determine which version is newer.
5 votes
- Don't see your idea?