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.
1440 results found
-
Include CPQ Favorite objects in the supported objects
CPQ includes Favorite objects as part of the package but Gearset doesn't support them. These can be shared proactively with users so they don't have to make their own Favorites. We make these in a sandbox along with new CPQ product configurations and would like to be able to push these up to production along with the new configs.
1 vote -
Let "member" create team-shared CI jobs OR let owner convert member's CI job to team-shared
I see currently only team owners are able to create Team-Shared CI jobs. When my offshore team members who have "Member" role need to create a new CI job, their only option is creating a user-owned CI job, thus missing the benefits of Team-Shared CI jobs. All of our org connections are already Team-Shared. And we already have a Team-shared VC connection too. So, it'd have been very helpful if non-owner users with "Member" role could create Team-Shared CI.
Alternatively, if that's not possible, next best thing would be - if team owners could convert any member owned CI job…
1 vote -
Let "member" re-authorize team-shared orgs connections
In our Gearset setup, we have tens of "Team-Shared" orgs, both production and sandbox. Whenever any sandbox gets refreshed, its connection in Gearset needs to be re-authorized.
Currently, only users with "Owner" role have this "Re-Authorize" option. Users with "Member" role don't have this option.
This creates a problem for my team. Since my offshore team is supposed to do these sandbox refresh and re-authorization tasks, and they can't do it unless I give them "Owner" role, and thus giving them admin privilege over the entire Gearset.
Thus, I'm looking for a way to let a non-owner re-authorize salesforce org…
1 vote -
Deploy the Name of object without truncating
Hello,
I deploy from Sandbox to Prod.
I have a custom object where the Name is 42 characters long on the Sandbox.
When I deploy, it has only 40 characters on Prod.
If I run compare, 42 on sandbox, 40 on Prod.
If I deploy again, still 40 on Prod.
I can of course change the Name by hand on Prod to 42 characters.
Thanks
Stephane1 vote -
Team members are able to create release with no access to CI job
Team members are able to create release with no access to CI job.
"Promote changes" is gray as expected, however "Create release" works which is awkward1 vote -
Unsubscribe from commit emails
Choose to unsubscribe / subscribe from commit emails (success and or failures) in gearset setup in order to avoid generating unwanted emails (and their PDFs) for each deployment (and save a little CO2 along the way).
1 vote -
Improve visualization of multiple features being simultaneously worked on in a single developer sandbox.
Currently, one must select (or create) a single feature+branch in the developer sandbox. The pipeline view only shows 1 active feature at a time. It would be nice visually see all of the features an individual developer is working on/assigned to.
1 vote -
Gearset Pipelines Sandbox Environment
In order to test new Jira webhooks, GitHub actions, and any other release management changes,
We would like a Gearset sandbox environment where we could test release management changes like new/updates to Jira webhooks, GitHub actions, and other related changes.
1 vote -
Display pipeline webhook errors in Pull Request details
Scenario:
- Feature branch created, commits added, Pull Request opened and pushed part-way through the pipeline.
- Pull Request has merge conflicts on one of the environments. Conflicts are addressed, but (let's say) PR fails validation so it is not promoted.
- New commit is added to the feature branch.This commit will generally fail to propagate into the above mentioned PR branch (triggering a webhook error). It would be GREAT if that error were somehow displayed on the PR details screen.
1 vote -
Customizable Messages for Jira Ticket Associations
When a Jira ticket gets a new comment from a validation or deployment, it's a pretty standard message:
Deployment succeeded: link...etc.
Deployment Notes:
Source: ----
Target: ----
And then a table of differences that were pushed through.My thing is, none of this is customizable, whereas I'd love to be able to potentially change what's automatically appended to our tickets to make it more user-friendly for the reporters on those tickets.
1 vote -
Query for Deleted Records
It would be helpful to have a way to query for all deleted records across multiple backup jobs for a specific object.
1 vote -
Allow tests to be run in parellel in multi orgs and allow aggregations of results for PR validation and speed up non prod deployments
We get 100 sandboxes, Can create test orgs org1, org2, org3 where our unit tests are split and run in them so hour long tests just take 1/3 the time? We would like it to be part of our pipelines as of now PR validation to develop takes 40 mins which makes it unustainable.
1 vote -
Help to have a change log, including the name and email of the person who changed the test level in CI jobs?
The test class level change in the job is crucial for us; if someone changes the test level to no test in place of a specific test run, components will go without a test run.
So, if we monitor things on a regular basis, we can ensure that everything is in place.
If we have a tab to get all these kinds of information, such as reports1 vote -
Gitlab Self Managed Issues
We suspect that reading the 'weburl' response field for the specified branch from an API call to GET 'v4/projects/$projectid/repository/branches' might be causing a problem when using public Gitlab proxies.
We suggest implementing a code change to compare the domain of 'web_url' to the self-hosted GitLab domain provided by the customers. The customer's self-hosted GitLab domain should take precedence.
1 vote -
Set up notification according to the target connection we're deploying to.
Set up notification according to the target connection we're deploying to. This way, the scheduled and manual deploys will notify us with what we set up.
1 vote -
Allow deployment of 'Check For Matching Records' in Flows.
As part of the new Salesforce Summer ’24 release, Salesforce have added the ability to check for matching records when using a ‘Create Records’ element. We’ve used this useful feature in various locations within our new flows to identify existing contacts for example.
When deploying the flows using this feature between developer environments via Pipelines or Compare & Deploy in Gearset, we’ve noticed that this new setting within the element doesn’t get deployed and is switched off in the destination org.
In the meantime, we can manually turn on this feature in the destination org.
1 vote -
Allow open PRs to queue up.
Allow open PRs to promote via selection and to queue up against the target keeping blocking behaviour to just merges and the deploy activity
1 vote -
Problem Analyzer should remove picklist values from record types when picklist values are removed from the picklist or value set.
When removing or deactivating a picklist value, Problem Analyzer should remove these values from any record types that reference them. While the initial deployment of the picklist may succeed, subsequent deployments of the referencing record types will fail if they still reference a deactivated picklist value.
1 vote -
Picklist Comparison should show if value is active/inactive
When comparing a picklist in which we have deactivated values, the simplified comparison visualization shows the deactivated values as being "added" (in green, on the source side).
The XML reveals <isactive>false</isactive> is being added, but the simplified view seems to suggest new values are added instead
1 vote -
New, one-click "Promote" button is very risky
In Deployment Pipelines when a PR for a CI Job is selected, a new, one-click "Promote" button exists, if the PR passes merge-conflict and validation checks. This new button is very risky in that it begins the promotion process, without recourse, when clicked.
Perhaps that's the designers intent but for myself at least, the button is too easy to accidentally click out of inattention, distraction or mouse clumsiness and is especially risky in that I cannot recall the action.
Personally I like the process of clicking the PR checkbox and clicking "Promote", which prevents unintended deployments.
As an alternative to…
1 vote
- Don't see your idea?