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.
1138 results found
-
Run Flow tests during test monitoring jobs
With the new flow tests, it would be nice if we could also have these run within test monitoring jobs.
5 votes -
Filter on UNselected items when choosing metadata to compare
When selecting metadata to compare, there is a picklist that says "Filters" and has an option for "Selected Only." Please add a second option for "Unselected Only" so I can quickly verify that I haven't left anything out without my eyes being distracted by checkboxes and items I know I already selected.
2 votes -
Add the ability to edit xml
I would like to have the possibility to edit XML files from the comparison view.
4 votes -
Allow delegated users to edit environment variables
My user is setup on our CI and I have a number of environment variables setup on Custom Labels for ID's.
Whilst this works great the main issue is if I am Sick/On Holiday there is no way for someone else to go in and add/edit the environment variables thus making me a single point of failure/Reference.
What would be great would be either have Environment Variables setup at a CI level and delegated users have the ability to go in and edit/create new ones against the CI (This would ensure only those that know what they are doing are…
6 votes -
Inline editing of metadata
The idea above was "closed" due to Environment Variables.
That feature is too fiddley for our use case as the change that needs to be performed is not consistent. Furthermore, that feature does not help with handling merges.
Gearset has some merging capabilities, but it only allows to select one file or another, instead of merging changes from both files.
I'm aware it is possible to perform merges from source control, though it would be easier to train our team if they did not have to learn another technology. Furthermore, it leaves the process to more faults as the…
6 votes -
Have the Jira ticket which was selected at the point of the commit stay with the PR in Pipelines
At the moment when you select a Jira ticket at the point of commiting to a branch, you are able to track that actionback into Jira.
However when a PR is opened from that feature branch to the next environment branch (in the Pipelines UI specifically) the Jira ticket association is lost, and has to be reattached manually.
Workaround:
- Put the ticket ID in the branch name, i.e. name your branch "feature/AL-99- new-flow"
- Use the drop down menu provided in the Pipelines UI to re select the Jira ticket
- Open the PR from the Commit successful screen and tick the…
2 votes -
Ability to see complete history related to a ticket or common name
It would be incredibly useful to have the ability to see a complete history related to a ticket or common name. For example, if I'm working on a Jira ticket named "SALES-123," I would like to be able to see all of the comparisons, branches, deployments, and promotions related to that ticket.
This ability would significantly improve the efficiency and effectiveness of troubleshooting issues.
1 vote -
Flexible Org Monitoring Notification Scheduling
I'd love to schedule a weekly or bi-monthly digest email rather than receiving emails for each run or each change. There are developers who need to know when changes are made, but they do not need to monitor changes frequently. In those scenarios, it would be nice to schedule out a weekly review of all changes.
2 votes -
Profile Comparison within Same Org
It would be useful to be able to compare profiles within the Same Org to allow for improved Security analysis and deployment.
Use Case: Developer added new functionality in Sandbox and applied it to only a few of the profiles that were specific to that story. Now there is a new to expose that functionality to more users, but need an easy way of knowing which profiles are missing the needed functionality without going through each individually.
2 votes -
Saved Comparisons should be visible to team members
I have a team that has access to Gearset but unfortunately they cannot view the Saved Comparisons I've created. To reduce unnecessary time spent on creating and maintaining Saved Comparisons, it would be greatly appreciated if the Saved Comparisons could be shared with the team and possibly allow the owner to delegate access to the Saved Comparisons.
5 votes -
Associated Work Items through Commit message
As a Developer, I want to use a unique ID from the work item I am working on
when I make a GearSet commit
So the work item I am working with (like Jira) can have a comment stating it was deployed
and I don't have to manually go to a separate process to update the ticket.Say my work items are in jira and I am working user story 100.
There is a Jira ID that is unique to that work item.When I specify a commit
instead of going through the separate process to find the work item…4 votes -
Compare Active Version of flows not the newest Flow
When comparing flows please compare the active version of flows, not the newest version. This would align with how change sets handle flow.
Example:
Version 2 and 3 exist in source. Version 2 is active and version 3 is draft. I want to deploy Version 2 that is active not the inactive flow.10 votes -
1 vote
-
edit problem analyser template
There should be an ability to edit the existing Problem Analyser Template. Else, one has to create the whole template again, re-do the changes on the template and then re-assign on all the existing Jobs which should use that template.
It is definitely going to save a lot of time and be beneficial overall.1 vote -
Allow Record type additions and removals to be selectable
I am not a having an option to deploy the particular picklist values in the Record type level, I would like to include only the values I have added that are different from my target environment.
3 votes -
Schedule deployment option for validation only CI jobs
It could be good that time selection schedule option is available, makes release timetable easier to execute to target org.
Currently user can only execute the pre validated package immediately.
2 votes -
Send Email when a package is Validated successfully with PDF of Deployment Summary.
We currently receive an email with deployment summary as PDF attachment after successful deployment, but we also want this feature for successful manual validation. This is help us review the validated package summary with Deployment approval teams in our ORG.
2 votes -
Only notify the Pull-request creator on validation errors
Hi team, not sure if there is a way to do that in the current setup, but I think it would be helpful to add the option to only notify the Pull-request creator/owner on the validation errors, instead of "hardcoding" the email recipients. Regards, Adrian
2 votes -
Enable a consistent, buildable set of Metadata for Releases
I'd like to have a way to work with a consistent set of metadata items for a release, that I can add, remove etc, and consistently deploy into a variety of sandboxes and ultimately Production.
Currently, if you clone a previous deploy, items are de-selected if they're the same between the environments being compared. That means once I've deployed, I can’t ever get that “list” of items back and I have to rebuild it every time.
A likely scenario is that I've deployed some metadata from Sandbox A -> B. Lets say it's 5 Apex classes. I then realize that…
1 vote -
language
Gearset UI Language specification. Allow users to specify which language they want the UI presented in and then show the correctly translated terms in that language. When using google to translate the UI the words it chooses are not always relevant.
1 vote
- Don't see your idea?