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.
1138 results found
-
inform users they're logged in somewhere else when failing concurrent logins
When a user might attempt to log into their account from a second computer (or VM), its appropriate to fail their login on the second computer. Right now, there is no indication that this has occurred because they're already logged in elsewhere. The error talks about adding Gearset IPs to Salesforce, but the issue is being logged in already.
I suggest telling us we're already logged in. It's easy to forget!
Thanks!
1 vote -
Filter branches by tag name
In order to remove the clutter when selecting a branch to deploy to or from, allow users to apply metadata filters that dictate which branches show up in Gearset. For example, being able to specify that I only want to see feature branches.
2 votes -
Searching for work item should allow for searching by ticket #
When searching for work items to associate to a deployment, user should be able to enter ticket IDs rather then key words from the Azure DevOps ticket title. This will make it easier to search larger backlogs.
2 votes -
Excluding Record Type Problem Analyzer Should Behave the Same Across Metadata (Layout Permissions, Custom Object Permissions)
In the situation where a repository is the source and an org is the target, there may be a situation where a record type doesn't exist in the repository but references in the layout permissions and custom object permissions do still exist.
Currently, the problem analyzer will catch the custom object permissions and ask you to remove the references to the record type that doesn't exist in the target.
However, it doesn't catch the layout permissions and the deployment could fail with an invalid reference.
In the absence of the record type in the repository, the "Problem Analyzer for excluding…
1 vote -
Schedule multiple gearset deployments
Have the ability to schedule metadata deployments along with data deployments. As of now, you must deploy all metadata then move into data deployments. It would be great to schedule these items in some sort of task flow.
2 votes -
Exclude specific Classes from Scheduled Unit Tests
Some Testclasses only run successfully, when the Org is connected to a Backend Application. Usually sandboxes for Development are not connected to the Backend. These are the Orgs, that we need to watch. It would be useful to exclude specific Classes on specified Environments from being tested in scheduled Unit Tests.
9 votes -
More granular permission settings for sub groups of a large team
Giving team owners/leaders the ability to define sub groups of team members and control their ability to deploy to certain environments.
For example not being able to connect to/make deployments to 'production' orgs.10 votes -
Allow searching Monitoring of a system by a specific record of metadata to see all the dates that the record changed
If I need to find when a specific thing was changed in our system, my only option is either to use the last edited date or to manually check every daily comparison from Monitoring to see if it changed. Since many metadata types do not reliably update the last edited date, it makes it much harder to find those changes. If I could choose a specific metadata record and use that to search the Monitoring to see when it changed, it would be much easier to find it.
8 votes -
Allow setting the default testing method for deployments
I want to enforce that any deployment into a UAT sandbox runs all the tests. The standard Default option runs no tests since it's a sandbox. I have to manually choose the "Run Only my Tests" Option every time I deploy to that sandbox. I would like to be able to have that option selected by default
2 votes -
Add new connection ends in loop
When I add a new connection via choosing "Salesforce authentication", I need to enter the username. I click on "Authorize". Instead of a redirect to the Salesforce login screen, I see a blank page with a gearset spinner logo. But this screen takes hours and will not redirect. I'm using Firefox and the Org is a sandbox (sandbox is also selected)
1 vote -
Add filters & search to the Salesforce orgs page
Add Filter/Search to the Salesforce Orgs page. On Deployment History you have a filter that is very handy when sorting through the list to find a specific deployment. I am currently trying to add multiple new dev Orgs for a client and it is hard to sort through them all. Can you add the Filter/Search option on the Orgs page?
2 votes -
Add a Description field in the General Settings for Automation like Continuous Integration.
We LOVE Gearset. I just took over when an employee on my team moved to a different team. I was looking over the existing Monitoring jobs and had to ask why some of them were setup. They were similar with the exception of when they run, for example. It would be helpful to have a Description field in the General settings section so when someone creates these jobs, they can give a brief description of their intent and purpose. Thanks.
1 vote -
Add support for "ServiceCrew" and "ServiceCrewMember"
These two objects are part of the FSL package for Salesforce. Right now, when we do a compare between two orgs, no results with be shown.
1 vote -
While configuring a data deployment, allow save after selecting objects and fields
There's no opportunity to save the data deployment settings after selecting objects and fields, and this can be quite time consuming, so if the job fails due to auth or other issues, right now, this requires the user to start over, and re-select objects and fields.
1 vote -
Throw Error When Invalid Test is Entered
When entering test class names in the text field, invalid entries can be added without any indication that there is something wrong, which would lead to uncovered code and most likely a failed deployment. For example, entering in ThisIsAnInvalidTestName would not result in any error.
10 votes -
More custom monitoring delays
It would be brilliant to be able to choose the days of a week your monitor script runs on so I don't have to deploy changes every single morning and could instead do once a week
1 vote -
Publish dynamic data with Outgoing Webhook in CI deployment jobs
As of now we are able to send only static text as a part of outgoing payload in CI Integration jobs. We want this data to be dynamic for each deployment.
For example: We need to send the information like (JIRA User Story number, GIT commit hashes and descriptions from the pull requests being merged, etc.)
This will allow us to publish information of successful deployments to external system.20 votes -
Integration with Rocket Chat
Hello, I need rocket chat integration, in order to receive notifications in deployment group chat about deployment status.
Thank you.
1 vote -
ability to filter on components
i would like to see the ability to filter deployments based on the components, just like the "Metadata comparison filter:" under Compare and Deploy option
2 votes -
Ability to clone deployments and include non-different (same) metadata items.
I would like to be able to Clone a deployment and include all of the metadata from the cloned package, even if there are no changes in the target org. This way I can incrementally build up a master package that includes all my metadata regardless of where I chose to deploy it.
1 vote
- Don't see your idea?