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.
1349 results found
-
Stop the reordering of XML when deploying to git
At commit to branch, Gearset reorders large chunks of the XML file. This causes additional deltas (seen in the hundreds of lines) and merge conflicts.
32 votes -
Show history of changes for a component
When performing forensic analysis regarding how or why something started working differently, it would be a great timesaver to be able to select a component and then be able to select the data comparisons for just that component. For example, select an apex class and then pick date dates so the system can display what changed. I would expect that this would be quicker than going into Monitoring Histories and picking each date and waiting for it to build the entire comparison of everything that changed and then having to find the component of interest.
A follow on to this…
1 vote -
3 votes
-
Remind repo owner to upgrade metadata on SFDC version change
Your blog post https://gearset.com/blog/mdapi-versioning-and-version-control says it all under the paragraph labeled "Upgradingyour repository's metadata"
But there's no real reminder to tell the team that this is a meritorious idea. My suggestion is that for the first 30 days after PROD is updated, you could display (in color) some alert (or maybe introduce a messages feature) wherein you tell the team that the repo's package.xml is out of date (version wise) with PROD version and provide pointers on how to upgrade, including nuances like Flows (v44).
It is too easy to get lazy and leave the repo metadata out of date…
1 vote -
Stamp a validated package with the username of the person who clicked 'Validate'
Currently, a validated package is created by the owner of the draft deployment package, even if someone else was the one to actually press the 'Validate' button. I would like to have the username of the person who actually pressed validation to be noted somewhere in the validated package for auditing purposes.
This would help us be compliant with processes where we need a record of separation of responsibilites bewteen users.
4 votes -
include the Name/ID of the Deployment from Salesforce into the Deployment Report generated by Gearset
Include the name/id in the deployment detail page within Salesforce in the Gearset deployment report so we can trace and match those details to a deployment run in Gearset.
4 votes -
Enable Defaults or Recently Used on Clone Deployment Page
When you clone a deployment package you have to select your Source details, but the selections do not default to the the last used settings or to a recently/commonly used settings. This is a minor annoyance but in other parts of GS you have the last selected options already selected based on user history, so hoping you can extend this to the Clone page
1 vote -
2 votes
-
Schedule data deployments
The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.
23 votes -
Export snapshot of production org to git
I'd like to be able to export a snapshot of all the metadata from my production org (include all components) to my git repository by clicking a single button.
After every release, it's worth taking whole metadata export from the org to git for the next/on-going releases.
For now, we have to create a couple of metadata projects to export the metadata to git, which is a tedious job and takes a lot of time.
1 vote -
Jira: Updating existing tickets with deployments using the standard Atlassian smart comment format
"[TicketID,...] some comment"
1 vote -
Deployment Notes Persist on Failure
When a deployment fails, deployment notes are sometimes wiped, and it is laborious to retype them - sometimes, I'll copy and paste to Notepad before deploying because I know I'm going to have to type them again. Notes should persist, or at least be configurable, from one comparison run through successful deployment.
2 votes -
create a visualization of the DevOps process
Creating a visualization of the DevOps process removes the need for separate Visio diagrams or visual aids to represent the process. Also by creating this feature, you could allow for a drag and drop type feeling to represent CI Jobs, Data Deployments, Comparisons, etc. Users who may be new to a DevOps environment would pick up the process quicker allowing them to quickly adapt to the tools and this type of deployment mentality.
2 votes -
Target Process Integration
Agile/sprint planning tool similar to JIRA
1 vote -
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 -
Link to test runs in Slack messages (or Slack messsage customisaton/templating)
I have automated test jobs post about failed tests to our Slack. I want the posted Slack message to include a direct (though maybe shortened) link to the "Test run details" so that when we see Gearset telling us about some tests starting to fail I would be one click away from seeing a view of failed tests the message is talking about.
Next/bigger step would be a way to shape the Slack messages ourselves. The most basic templating setup where I could write my own Slack message with some placeholders like {{instancename}} or {{failedtests_link}}..
8 votes -
Store formatted JSON in source control
The SFDC metadata API returns some items types as JSON compressed to a single line. For example, this applies to Wave dashboards (.wdash files).
Gearset neatly expands this to a more readable when visualizing and comparing.
However, in source control Gearset stores them in their original one-line compressed format. As a result, when doing merging and conflict resolution at the source control layer, these items are impossible to handle, as any change (whether technically conflicting or not) results in a conflict from git's point of view.
It would therefore be great if Gearset kept the expanded format for JSON data…
2 votes -
Selection Count Mismatch
The Selection count on ‘Compare and Deploy’ page doesn’t match with ‘Items Selected’ on ‘Draft Deployment’ when a draft deployment is opened. Having this in sync will help user that all selections are going in the deployment.
1 vote -
Queue Deployments
Current State:
A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org
1st Dev deploys work to .dev
2nd Dev deployment fails because org is locked
Idea:
A few devs have work in their individual sandboxes that are ready to be pushed to the higher .dev sandbox org
1st Dev deploys work to .dev
2nd Dev deployment is queued up, 2nd Dev will be notified via email/browser when queued deployment has started
3 votes -
Give Permissions to Edit Automated Job Settings
Adding a feature to give users permissions to edit & delete Automated Test Jobs would be great. Today I had to hunt down a colleague to be have him edit his job when all I had to do was change the schedule. This feature would have saved a lot of time.
2 votes
- Don't see your idea?