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.
-
Permission sets not deploying correctly
When deploying a permission set, it was being deployed without the permissions checked, even though Gearset detects that the permission is checked in the metadata compare.
3 votes -
Summary pages should always include ALL changed files
I believe this to be a bug, but it might be intentional. In any case, the current functionality is, in my opinion, poorly conceived.
If a user adds a deletion to a comparison between an org and git, the deleted metadata is the only item that will show up in Gearset. However, if you inspect the resulting commit in git, you will see that the metadata was deleted along with all of the profiles, layouts, etc that had to be changed as a side effect.
I'm completely fine with Gearset detecting these dependencies and making the changes to them. It…
1 vote -
custom object translation of the Product2 object
The custom object translation of the Product2 object, specifically, is not behaving like the other custom object translations. So when I changed the label of this standard Object : Product2 (Set-up -> rename tabs and labels)
i can't find it in Gearset. I have to make this change manuelly.1 vote -
When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
5 votes -
Issue with Namespace while deploying from Org A to Org B
the namespace if referred in code, we try to deploy to target Org, the target Org will not have the same namespace name, or will be a different namespace, it gives errors, can something be done to fix this?
1 vote -
Deployment of pre-valided package doesn't include accurate test counts
We did a deployment last week and noticed that as part of the deployment report that went out that it stated the Tests Run was zero. We did a pre-validation the day before where we ran all tests with all passing.
Could this test section on the deployment report again include/include the pre-validation tests that were run for the deployment?
3 votes -
"Changed on" date on source control side of comparison does not show
We have no way of knowing when the files were last changed on the source control side. Tried only with BitBucket though.
9 votesThat is something we should definitely show. We’ve added it to our investigation list to see if it can be added into the app.
Thanks,
Jason. -
Changing executing time in a Job does not automaticalely start the Jobs!!
No information is given!!
1 vote -
Suppress "changed on" datetimes in difference viewer where datetime is the same as the metadata retrieval datetime
The difference viewer will show Changed on values for the current datetime for certain metadata types - probably because SFDC is returning such a value when, in fact, the source didn't change at all
- Custom object
- Settings
- Standard valueset
- Workflow rules
displaying the current datetime of the compare run (i.e. the metadata retrieve datetime) is not helpful when trying to filter on changed date in the difference viewer (i.e. sort descending)
3 votes -
Deployment count in the blue banner wrong for old deployments
When viewing old/past deployment details, that old deployment shows me the big blue banner saying that ---this--- was our {insert total number of deployments ever}th deployment no matter which old deployment I'm viewing.
This confused me a bit because I wanted to view our say 5th deployment ever so expected the number to say this was our 5th deployment, and I ended up closing the details browser tab twice thinking I pressed the wrong button to view the latest deployment. Yeah I could have looked at the tiny timestamp somewhere on that details view, but this large blue banner/counter just…
1 vote -
Make "Clone package" openable in a new tab
In Deployment history, there are two buttons I use the "view details" which I can open in a new tab without leaving the list of deployments, and the "clone package" which I can't open in a new tab. I can workaround it easily (duplicate tabs, or first view details then clone from there), but it was disappointing that I have to.
I needed to re-deploy say 10 deployments into a different sandbox and so the clone package feature was amazingly useful, but this little nag prevented me from entering the blissful nirvana of wielding the perfect tool for the job…
1 vote -
Optimize comparison list view
The comparison view contains a list view in a scrollable area with an line item for every metadata item in the comparison. Depending on the comparison, this list can be exorbitantly long (10k+ lines). Displaying this many elements on screen is extremely inefficient, and causes browsers to lock up when selecting the "check all" check box (because it results in thousands of incremental manipulations in the DOM). This issue also causes mobile browsers to crash when more than a thousand or so items show in the comparison results.
There is a common pattern for handling long lists like this, in…
1 vote -
Better error message when refreshing draft deployments created by another user
Currently, if source control is either source or target and User A creates a draft deployment bit user B wants to refresh that draft deployment, you get an error message: "Error occurred during operation: Determining API versions - An unknown error occurred."
As this capability isn't currently supported by Gearset, there should be an error message when the refresh comparison button is clicked saying" Refresh is not possible when Source control is involved except by original creator of the draft deployment"
1 vote -
Include a field's permission if the field is flagged as a missing dependent component
If a field is identified as missing from the deployment and the user agrees to include it, the corresponding field's permission should also be added.
2 votes -
bug -- Refresh comparison with a selected item that on the refresh is no longer changed
If you have a piece of metadata that was changed on a comparison then a subsequent comparison using the 'Refresh Comparison' button. The selected item is still selected and unable to be deselected.
1 vote -
Include custom metadata type (__mdt) listviews
Not sure this is a bug or a limitation in the V40.0 SFDC Metadata API but it would appear that Custom Metadata Type (__mdt) listviews are not included in the Comparison (default 66). List Views on other Sobjects are included. Hence they can't be deployed
1 vote -
View email templates that are part of a managed package folder in comparison
Hey guys,
I am not sure if this is an actual issue or not but I will ask the question to see if I am missing something :)
When comparing email templates, the compare will return both email templates and folders. I have noticed that in my case, email templates that are part of a managed folder do not return. We can see the folder and sync the folder settings, but no templates. If we move the templates to a non-managed folder we can see the templates. Has anybody encountered anything similar?
Thanks!
Richard
1 vote -
Page Layout Deletion Not Detected
When I remove a page layout from my Git repository (the file and the package.xml entry) and then do a comparison to an org that it still exists in, Gearset fails to detect a deletion. It doesn't even show up in the All objects tab. It happened to me yesterday and then I just reproduced it now.
2 votes -
Properly handle SFDC change of API name for Order "Activate" button on layouts
CustomObject 'Order' Page layouts from orgs created from orgs prior to V39 may have in the layout metadata <excludebuttons>Activate</excludeButtons>
For V39 (and possibly earlier) orgs, 'Activate' is no longer the OOTB API name for the button with label 'Activate'. The button API name is ActivateOrder. Hence, deployment fails with error "In field: excludeButtons, no such standard action:Activate"
There is no workaround except to exclude the Order layout from the Gearset Selected Objects. This is not a good workaround for a commonly-used OOTB SFDC Standard object.
1 vote -
The number of differences does not appear to the left of the Prev/Next buttons in XML view mode
However, the number of differences does appear when viewing the same Apex class in APEX view mode.
2 votes
- Don't see your idea?