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.
1304 results found
-
sandbox seeding size
When deploying data to sandboxes, it would be helpful to get an approximation of the amount of data and file space a seeding job will need. I have on numerous occasions hit storage limits as a developer sandbox only has 200 megabytes of usable space.
1 vote -
Add an option to ignore ".forceignore" files
When a repository contains a forceignore file, deployments to that repo will not include these elements.
Sometime however it might be necessary to explicitly deploy these elements (e.g. manually).I propose to add a flag "Ignore .forceignore" at least for manual comparisons + deploys to be able to still push generelly ignore components to the repository.
1 vote -
Show duration for comparison jobs
While the Comparison History screen shows when a comparison job was initiated, it would be extremely helpful to display the duration of that comparison job, from when it was initiated, to when it was completed.
Ideally, this would show on the Comparison History screen, and/or on the actual Comparison screen itself after it was completed.
1 vote -
Seed Data alongside Feature Branch Promotions to Orgs
The idea is to bundle the data that should be tested along with the feature branch, so that once a story is deployed the data is also available (similar to one of Copado's features).
This allows us to test regardless of dev, partial or full copy sandbox type. Allow for a set of data to go along with a feature for testing reports and analytical tools. Possibly integrate existing Seeding Templates that can be paired with a feature branch. Allow for configuration of data deployments to environments through the CI job for feature+data deployments. Allowing some environments to refuse the…
1 vote -
Add navigation into elements of LWC bundle in difference viewer
The current LWC difference viewer shows the components linearly from top to bottom - meta, css, html, js. Just like you did with the side bar navigator for layout, add a side bar navigator for the LWC bundles
1 vote -
Allow developer sandbox updates to be qued instead of failing
When you update developer sanboxes you can only do a max of 2 at a time or else the extras fail and do not automatically retry when the other are done. I would like if they would just enter into a que so that you could click update on all of them and not have to wait until the first 2 are done to then click the next two.
1 vote -
Update all developer sandboxes with one click
Deploy updates to all developer sandboxes with one click
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
Promotion PRs should show the original author on GitHub enterprise
Hello, according to the documentation here - https://docs.gearset.com/en/articles/8545155-why-are-my-prs-showing-the-pipeline-owner, promotion PRs created by Gearset in GitHub can show the original author of the PR. After talking with support, they told me that this feature is not supported for GitHub Enterprise. Could this be made available in Github Enterprise, as it is now in GitHub?
1 vote -
Git Delta Deployment
I think it would be great if Gearset pipeline feature changed to do a pure Git delta deployment instead of a Git/Org delta deployment. The reason for this is that then you only deploy your work (or what has changed) instead of deploying potentially any differences between the given branch and your org. Here's more information on this concept: https://developer.salesforce.com/blogs/2021/01/optimizing-unpackaged-deployments-using-a-delta-generation-tool
1 vote -
Auto pull in Commit descriptions into pull request description
Create a button in the pull request creation screen that allows you to pull in all commit messages into the pull request description field automatically.
1 vote -
Prevent Pipeline Paths from crossing Static or Developer environments
Sometimes depending on how you setup the pipeline you can end up with pipeline paths crossing/going under static environments and developer sandboxes.
This gives the impression that they are connected when they are not.
I would like it to look like this: https://drive.google.com/file/d/1s59BS47wEuHFA8Grb0SLdFSH00AgWw0W/view?usp=sharing
But it ends up looking like this: https://drive.google.com/file/d/1BLFrHd0HTR9LTLSoUw_34BqAWgvDa1SO/view?usp=sharing
1 vote -
Darkmode option
It would be really helpful having a dark mode of gearset UI. A big number of devs prefer dark mode over bright mode. Since gearset is a tool mainly used by devs, would be good to give to devs the option to customize their UI.
3 votes -
Automating/Scheduling DevSandboxUpdate aka Back promotions in gearset pipeline
Automating/scheduling DevSandboxUpdate, aka back promotions in the gearset pipeline, sometimes it becomes challenging for developers to update their sandboxes whenever there are frequent releases to production in a short span of time.
1 voteThis is currently planned for later this quarter and next.
Users will have the option to:
- Bulk update selected dev sandboxes
- Automate developer sandbox updates; they will be immediately tried as and when ready
If users want to automate dev sandbox sychronization now, they can use CI jobs to deploy changes from their desired source of truth - this comes with some risk of affecting work in progress though.
-
Add more information regarding team shared metadata filters
Hello, I have the following suggestion.
When a team shared filter is created, it would be a good idea to see who is the user that initially created it.
Also, it would be beneficial to see who last modified it and when was it last used.When we have a lot of team shared filters, such functionality will greatly help with the clean up efforts.
1 vote -
Show "When to Run the Flow for Updated Records" in Flow previewer
For record-triggered flows you either set the flow to run
1) Every time a record is updated and meets the condition requirements
or
2) Only when a record is updated to meet the condition requirements
It would be helpful to view these settings within the flow previewer window of a comparison.1 vote -
Show "When to Run the Flow for Updated Records" values in the flow previewer
For record-triggered flows you either set the flow to run
1) Every time a record is updated and meets the condition requirements
or
2) Only when a record is updated to meet the condition requirements
It would be helpful to view these settings within the flow previewer window of a comparison.1 vote -
Install managed package from sfdx-project.json
I would like to get the possibility to track my managed packages and their versions in the sfdx-project.json file and automatically install it from this file. Could this be a possibility?
1 vote -
Add sharing to comparison view
When you look at the comparison of the list view the "shareto" metadata is not available in the nice clean view. Its only available in the XML view.
1 vote -
I would like to download a CSV file from any stage in the Pipeline that includes all the PR details.
I wanted to know the PR's that are pending between the pipeline environments, so I copied the screen data into a spreadsheet and had to spend time to make it usable. I used the information to understand the outstanding work by team (we follow naming conventions for our work), identify stranded stories from departed developers, and have a deeper understand into the backlog. I am using the information to talk to the pod leaders discussing process improvements, release timing/scheduling, and other operational improvements.
1 vote
- Don't see your idea?