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.
240 results found
-
Ability to change Formula Fields to other Field Types
Gearset doesn't help with one of the most common deployment headaches: changing a formula field to a non-formula field type. It's still a nightmare even with Gearset.
What would be awesome would be if you had a "Change Field Type Wizard" where we could say FormulaField1 needs to become TextField1 and it would do multiple deployments to accomplish the changeover:
- get components
- deploy temp field of new type AND update all existing components to reference the temp field instead of the formula field
- deploy delete of formula field
- deploy text field in place of the old…3 votes -
API to provision users, assign users to connected organisations
API to provision users, assign users to connected organisations
It would be hugely benificial to us (60+ connected organisations, 25 employees working in teams for multiple clients at a time) if we could programatically provision/deprovision users and provide access to connected organisations via an api.
At the moment this is error prone manual work that has to be done by someone with high level access (and as such is usually already short on time).
6 votes -
call webhook with scheduled deployment
We would like Gearset to call a webhook when a scheduled deployment completes. The message to the webhook should pass a message with the org name, UTC datetime, the deployment friendly name, URL of Gearset deployment results and a status field with 'succeeded' or 'failed'
3 votes -
1 vote
-
`Deployment history' User Interface update.
In `Deployment history' it would be great if when you choose a target and it opens in a new window. Deploying 48 packages and it is painful.
1 vote -
Include support to name space filter to include option to include unlocked packages with no namespace
Currently there is no way to retrieve and compare components belong in an unlocked package with no name space without using the 'include managed package' namespace filter 'all' option.
this might include too many items that I am not interested in.
4 votes -
Modify the "Changed On" drop down filter groupings to round to the nearest day, rather than the exact time the change was made.
It would be helpful if in the "Changed On" dropdwn filter if it grouped it into days, rather than the exact time the change was made. Also, if there were preset groupings like "Today","Yesterday","Last 7 Days", etc.
5 votes -
Deploy permissions for Lightning Record Pages
provide a means of deploying the profile/recordtype/app permissions for lightning record pages without having to deploy the whole app.
4 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 -
Clone Package - keep Tests list
It would be great if when cloning a deployment, it can keep the tests which got performed in the original deployment. Right now, we need to keep a list of the tests which ran on a doc on the side.
3 votes -
Support VS Code extension: ForceCode
Can you please support VS Code extension (ForceCode) source format so that we can use the extension to commit and include in CI jobs.
1 vote -
Email2Case Deployment for Selected Email2Case Setting
When deploying email2Case i am unable to choose particular email2Case that i need to deploy and end up choose all the email to case settings. Needed feature to deploy this selectively.
1 vote -
Plain text list export of metadata
There are times when I'm in an email thread with other developers and I want to share a list of metadata that I'm trying to deploy via Gearset. It would be nice to have a button after a validation or deployment (failure or success) that copies in plain text a list of everything in the deployment. The list not only has the name of each metadata, but also the type of metadata it is.
1 vote -
Reporting
have a way to dump a csv of the description of objects. i need to find a way to see what fields are encrypted.
1 vote -
Separate Filters for CI Jobs to reflect filter edits
Currently, if you have a saved filter being used in CI jobs, any edits/changes to that filter are not reflected in the CI jobs that use said filter.
It'd be great if we could isolate filters for CI jobs so that we could edit CI job filters that would then affect every CI job they're being used with instead of having to edit every job and re-select the filter whenever a change is needed.
4 votes -
track metadata filter changes
Filters are shared by default. However, if someone changes the filter, I cannot tell what has been changed, who made the change or when it was changed. Ideally, I'd like a version history for each filter.
3 votes -
Meta Data Searches
Ability to do a meta data search like you can in eclipse or visual studio in gearset.
For example search a custom field and where it is used within your org.
1 vote -
Inline Editing of metadata
Inline Editing of metadata
In order to make our deployment successful we had to download the package, modify the version numbers on the flow definitions, and then compare the local package to the target org. It would be very helpful if we can edit the metadata XML in the UI so we can fix the version numbers.105 votesHello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
-
Allow the use of cached metadata during comparisons
Over the past 2 days we ran multiple comparisons between salesforce orgs. Nothing was changed in the target org but some fixes were applied to the source org in order to make the deployment successful. A lot of time would be saved if we had the option to compare the source org to a cached copy of the target org. In this case, the source org was finishing very fast, especially when we used the local file comparison.
2 votes -
Provide the ability to run static code analysis on all commits to the repo
We'd like the ability to run static code analysis on all commits to a repo, regardless of the branch name. This would allow us to catch code quality issues early and up front, regardless of the branching model we use.
Example: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow (development is done in feature-* branches, so there's no one branch we can configure a CI job on)
1 vote
- Don't see your idea?