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.
1413 results found
-
Change the Metadata Filters and make them first class
I would like to see a change to the metadata filtering in general.
Filter management has become a important part of our devops process as we seek to lower our comparison timing.
Instead of having it at the bottom corner of the compare screen, move that section to the middle of the compare screen.
In addition, add a side bar specifically for filters that allows you to edit or delete them as well as change the sharing between personal and team. I have example screenshots for suggested layout changes here: https://faef.box.com/s/frse8jnvqsxbl8ue05x641j3wlga1quy6 votes -
Allow serial deployment instead of parallel
When executing a data deployment, an 'Unable to lock row' error can occur if multiple transactions try to lock the same record in Salesforce.
Because the batches are executed parallel, the chances of getting this error high, depending on the situation.
For example the master record in a master:detail relationship will always get locked when a DML is executed on the child record.
If two batches are executed at the same time and they both have at least 1 record that references the same parent, then a locking error will occur.6 votes -
Add ability to clone deployment CI job to validation-only CI job
This would save us time duplicating regex statements for the new job
6 votes -
Allow CI jobs to validate PRs of a branch into Separate Scratch Orgs
Currently CI jobs can only validate PRs into a regular org. So if you have multiple PRs raised to that branch then you have to wait as they each run one after the other. If we could validate into separate Scratch Orgs instead then all the PR validations could run in parallel and it would speed up validation
6 votes -
Archive or hide Automation jobs
On each of the Automation dashboard views (Monitoring, Unit testing, Continuous integration) it would be nice to have a way to archive or hide job. Often times previously setup jobs that are not active but would be good to keep for historical reference can clutter the dashboard.
6 votes -
Don't change the first 2 rows of a metadata file in version control
Usually a Metadata file retrieved from Salesforce starts like this:
<?xml version="1.0" encoding="UTF-8"?>
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">So two lines, first with the version and encoding UTF-8 and second with the type of metadata.
Now when GearSet does the deployment to version control, either from an Org or a Branch it uses this styling of the first row:
<?xml version="1.0" encoding="utf-8"?><PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
So everything on one line, with the encoding in lower case.
I don't see a logical reason this should be different in the files and is then causing differences in the version control system.
Thanks for looking into this.6 votes -
Options to pick only selected custom labels metadata for salesforce.
Since the custom labels metadata can’t be picked individually, the Gearset compare and validate process would pull in all custom label changes. This would be a concern if we want to withhold any particular custom labels from being pushed to higher environment.
6 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 -
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.
6 votes -
Suppress irrelevant Suggested Fixes when deploying to git
The problem analysis comes up with a number of Suggested Fixes which may make sense for improving Salesforce deployments, but which are unproductive when applied to git deployments.
For example, the suggestion to remove TASK.WHAT_NAME, or to omit Standard Objects, will only serve to create a git repo which is an inaccurate reflection of the source org. Each time we deploy to that git repo, we will continue to have the same changes to select or omit, since the repo is missing objects and fields from the source org.
When the deployment target is a git repo, all suggested fixes…
6 votes -
Display the Filter used in the Comparison history screen
It would be helpful in finding the right comparison to look at if you could see on the Comparison History screen which filter was used. It would also be helpful when looking at the comparison details to know which filter was used.
6 votes -
Show Created By and Created Date when doing comparisons
When looking at a comparison it shows changed by as a column, would be helpful for consultants to Show Created By and Created Date as well
6 votes -
test class not captured in deployment history
It would be nice to capture whatever test classes ran for code coverage deployment of classes/triggers in the deployment summary in the Test Results section. You already have a section for this test results so why not add the class names used in the report. We have come across many classes deployed without their appropriate test classes and it is hard tracking/documenting which test classes were used to deploy these as there are no documentations in the class.
6 votes -
6 votes
-
Allowing data deployments in CI jobs
Allowing data deployments in CI jobs. So that configurations in third party apps and B2B Commerce can be deployed as part of CI.
6 votes -
Filter on selected items
I want to quickly be able to identify components that have not been reviewed by only seeing unselected items in the "Changed items", "New items" and "Deleted items" top level filters.
seeing the ones I have already selected slows down productivity and I have to scroll through them. If I want to see them I can always look at the "All items" section. This information is also available in the difference type column.
6 votes -
Select all objects in a data deployment
It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)
6 votes -
Jira: ability to associate tickets during comparison
Would like the ability to associate Jira tickets during the comparison process so that it can be saved to draft deployments and can continue to add as needed. Currently it appears you can only add Jira tickets after you have finalized all items for deployment.
6 votes -
Extend Jira Cloud Integration to Releases and Bitbucket
We do the majority of our management via Jira and have it linked to Bitbucket and our test system so that we can manage everything via Jira. It would be great to extend the current integrations to more intelligently link the package to Jira tickets and the corresponding Bitbucket code and then push back to Jira the deployments in a more Jira friendly manner e.g. potentially creating/updating a Jira release for the deployment.
6 votes -
Provide the option to skip problem analysis
Sometimes during a complicated deployment I need to try a few different strategies to get things to work. For example, I may need to just send up one piece or set of metadata up first.
The problem is, each time I do this, I have to wait for problem analysis to complete, which takes a couple minutes. Normally during a deployment I do want problem analysis to run, but if I want to quickly send up a single object, I have to wait a few minutes while Problem Analysis runs, and the time waiting adds up.
Maybe a quick deployment…
6 votes
- Don't see your idea?