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.
1152 results found
-
Allow XML comparison to be exported
Being able to extract the XML for the change and the target's differences would allow us to analyze and track label/code changes versus just ordering or location changes.
My issue is similar to the "Enhance XML meta data comparison to ignore changes in XML order" and "Export Comparison details all items" and "Allow download of XML files from the comparisons page"
1 vote -
Search with components returned by metadata comparison
Performing a search across the returned components xml would be helpful. In our org we add a JIRA ticket reference to the Description - having the ability to search for the ticket number string would help narrow the list.
1 vote -
Option to create a CI job only for back propagation
We created some CI jobs for back propagation of changes from Production to other downstream branches and orgs. But these CI jobs also pick up pull requests(from a different pipeline) for forward propagation.
So, basically there is no way currently to create a CI job just for back propagation. It will be good to have a toggle in the CI job to mark it for forward or backward propagation5 votes -
Show PR Flow changes in Flow Navigator View
New new Flow Navigator view is really good.
It is such a shame that I am only able to view flow in flow navigator in comparison view (when creating pull request).
I would love to be able to open flow in flow navigator directly from teammates open pull requests. That would really speed up reviewing flow changes cuz reading metadata on VCS is not the clearest thing to do.1 vote -
Soft delete User accounts
If you ever delete a user then that account can never be used again or added back. Rather than provide a warning with text that not everyone is going to read it would make more sense to not even have the delete option in the first place or do a soft delete where it can be reactivated. We have employees that have left the company and returned so its not an uncommon scenario. If someone leaves or an account gets deletes accidentally it would be nice to have some sort of recovery option then to not allow that email address…
1 vote -
deploy user records via REST api
Currently there is no way to deploy user records via Gearset because the Data Deployment feature uses the Bulk API. This is painful for those cases when we have sandbox testers that we need to move between sandboxes!! Please add the ability to deploy users via REST API.
1 vote -
Increase API call limits
There currently is a API limit of only 10 calls per hour for the reporting and audit API's. This makes it difficult when developing and testing applications that tie into the api. In our case we use the api to pipe the data into our observability platform for reporting and dashboarding. It would be nice to either increase to something not THAT low or to have a development override option of some sort that customers to request to temporary increase. I understand the need for some limits due to having a shared cloud platform but this seems to be on…
1 vote -
Precision Deployments for Flow
Please add Flow for Precision Deployment. The new flow visualization has been really great and it would be very helpful to be able to use precision deployments with them.
6 votes -
Expand Notifications Capabilities
Currently 'Notifications' found under 'Settings' in 'My Account' allow for send outs for your owned connections. It would be helpful to have the ability to make notifications for connections that have been delegated to you as well.
1 vote -
Grouping developer sandboxes in Pipelines - back-promotion to a group
Team,
Currently Gearset Pipelines only offers the option to connect a developer sandbox group to a single downstream environment. While back-promotion to a group isn't available yetCould you please enable it ?
3 votes -
Ability to move existing field to be under another section on layout
If I have multiple sections on my layout.
I have a specific field under one layout section, but now I changed the layout so the field no is moved to another section.
Now I can't do that because the compare and deploy forces me to override the existing section where the field is under.
My intention is to move the field place to be under another section and not delete the other layout section1 vote -
Please adjust problem analyser feature to show record type changes when a picklist field value is added.
Currently Problem analyser does not show any warnings or issues when record types are not selected for a picklist field changes( value addition). With this during deployment there is fair amount of chance that some one could easily miss record type changes. Please adjust problem analyser to account this situation and show record type changes as warnings would be beneficial.
1 vote -
Ability to Customize Export Items in Comparison
Currently we are able to Export All of our comparisons. It would be a nice addition to have the ability to customize the export. For instance, as the GearSet user, I would like to be able to export specific items. I would also like to be able to include either the "depends on" or the "used by" items in my export as well as the specific items that are used or depended on.
IE:
In my export, I have selected Object A, Object B, Object C, Report 1, Report 2, Report 3, Flow X, Flow Y, Flow Z. In total…1 vote -
Add exclusion filters for Pipelines
Currently, the metadata filters in pipeline (CI) jobs are either all of a type of metadata, or a defined subset. There is no option to include all, except for a couple of objects, which is oftentimes required.
Please consider adding a negative (exclusion) filter for CI jobs, in addition to the existing positive (inclusion) filters.1 vote -
new comparison tool issues
new comparison method/view has a few bugs/bad ideas
when selecting a comparison pair & comparison filter on the "saved comparison pairs" page, the chosen filter does not carry through to the new screen & has to be re-applied
once in the comparison screen, there is no "sele3cted" button like on the legacy page. - this is crucial to know where I'm up to with selecting the parts to release.
2 votes -
Include DataWeaveResource in comparisons and deployments
DataWeaveResource has been around for a few releases and is deployable via the Metadata API, but is not supported by Gearset yet. Please include this.
1 vote -
Persist Selection to Include/Exclude Managed Packages in Compare 2.0
When using the new compare, the default is to exclude managed packages. However, we'd like to always include them, so it would be nice to persist the selection from one compare to the next.
1 vote -
Adding Identity Settings to Metadata Deployment
Would be nice, if the Identity Settings can be deployed. Currently, every change on any Identity Settings page has to be done manually in each org.
1 vote -
1 vote
-
Allow us to update the Associated Azure DevOps work item on a successful deployment
Currently within the successful deployment page, you can edit the 'Deployment friendly name' and 'Deployment Notes' which is a very handy feature.
However sometimes we would need to also update the associated work item as the wrong one can be mistakenly associated, this would be a very useful feature for us as a way of correcting such mistakes (that are in fairness rare).
1 vote
- Don't see your idea?