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.
31 results found
-
Validation-only deployment for CI
Add the option to for CI to run validate-only deployments
2 votes -
Add column filtering with org type(s) in deployment history
Ability to filter on org and/or org type in deployment history so we can easily view which deployments were made to which orgs. For example, filter to only return deployments to production orgs.
2 votesWe’ve now added more advanced filtering to the deployment history page to enable multi-selection. You can find the filter menu via the dropdown next to the text search box.
-
Improve the doc page: Fixing a feature that’s halfway through the pipeline
The procedure as written seems complex and counter-intuitive
Given that a developer sees the process as DEV->Integration->UAT, if an error is detected in UAT manual or automated testing, the fix should flow from DEV -> integration -> UAT.
But the article has the fix going from DEV->UAT and then back propagations back to Integration plus manual PRs created in VCS. This seems way too complicated and hard to understand for a mere admin or junior dev
1 vote -
Clone CI job without delta enabled
As the Gearset administrator for my team I want to be able to clone a CI job that is set as a delta job without the delta flag enabled so that I have less effort to create a brand new CI job.
Acceptance criteria:
- When closing a CI job with the delta flag enabled, give the option for the new job to now have the delta flag enabled.
- If the source and target are the same as an existing job, provide a visual warning of the potential consequences of replication of the job.
1 voteHi, this feature has now been released.
When cloning a CI job with delta enabled, you should now be able to toggle the delta CI checkbox when configuring the cloned job -
ci owner
Allow CI jobs to be reassigned to new owners. Or allow for out of office functionality when CI Owner is out of office.
1 voteCompleted on March 6th, 2020 see documentation on https://docs.gearset.com/en/articles/3758806-transferring-ci-job-ownership
-
Update package.xml with destructive changes which helps CI jobs
When I commit components to bitbucket brach if I have 5 new components and 5 deleted components. then Gearset is updating package.xml in the src folder with only 5 components which are to be created but destructive changes are tracked no where. Then if we deploy from this branch changes to Sandbox using CI job which has 'Filter metadata changes using package.xml' checked, then the deleted components will not be deployed. It is good if Gearset give a feature to track destructive changes and deploy using CI job.
1 voteCompleted on October 29th, 2020
-
Github Pull Request as a `Draft`
This new feature is great. Would be even better if you can select that the PR be a draft.
1 voteHi,
You’ll now see the option to create a draft pull request in GitHub, if your repository supports draft pull requests.
Draft pull requests are available in public repositories with GitHub Free, GitHub Pro, and legacy per-repository billing plans, and in public and private repositories with GitHub Team and GitHub Enterprise Cloud. For more information, see https://help.github.com/en/articles/about-pull-requests#draft-pull-requests.
-
allow for the ability to "lock" a metadata filter in for a CI job so that the CI job has any changes to filter.
Currently, the CI job takes the current metadata filters settings but does not used the updated settings. You have to re-add the filter back to the CI job. If checked on the CI job, the job would use the current filter's latest changes rather than the ones it was created with.
1 voteYou can now edit the CI job and choose to simply refresh the filter list so it grabs the latest changes to any of the filters and as a result will let your CI job use the most up-to-date settings.
-
Change CI Job Design
Your new CI job design is horrible. I use disabled CI jobs as one button deployments. You've just doubled the number of button clicks I have to do for no good reason. Run Job should be on the main bar.
1 vote -
Remind me what I just validated
I am working on 10 things at the same time like usual. I started a validation about an hour ago. I open the tab where the validation was occurring and it says it succeeded. Yippie! Problem is I don't remember what I was validating and nothing on the success screen tells me which system I was validating against. I want to be sure I am going to deploy the right thing to the right server at the right time.
Can you add the name of the destination system (at least) on the success screen so I can remember what I…
1 voteThis information is now displayed on successful validation.
-
Add button to go from validation package to comparison
Use-case is where we have validated a package, but not been able to deploy it before expiry. Eventually, we are able to deploy it...
At this point, I'd like to be able to go from my validation package in the history straight to a comparison with the same objects selected. Then, I'll be able to make sure everything still looks good and validate/deploy again.
1 vote
- Don't see your idea?