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.
1140 results found
-
Allow components to be added or removed from an data deployment template
Currently when a data deployment template is created, there is no way to edit the template after it is saved so that components can be added or removed. It would be helpful if we could modify the components in the template without having to create the template from scratch again.
19 votes -
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
How about a default BitBucket repository on the popup page that appears when you clone a package (under “Deployment History”)?
2 votes -
Attach pdf items details in the email notif "Your organization has changed"
When you receive a notification concerning a change into an organization you need to know quickly which items are changed.
4 votes -
display meta data filter used on deployment report
It would be useful to see the meta data filter used on the deployment successful report
2 votes -
Only display active branches when displaying branches from a bit bucket cloud repository
Only display active branches when displaying branches from a bit bucket cloud repository
5 votes -
Allow CI deployment notifications to the specific user who made the source control commit that prompted the deployment
We have CI jobs that fire on commits to a source control repository. At the moment, there is no way to email the specific individual who made the commit that prompted the deployment, so we have to notify everyone involved in the project whenever a deployment fails. If we could just notify the individual who made the commit (plus the deployment manager), it would reduce noise considerably.
Please add this feature.
13 votes -
Allow run tests not only by specific name but by regex
We have a lot of tests and it takes about 2 hours to run them all. But we also have some small services almost completely isolated and which have a specific test class name convention. Currently, we're using ant to specify which exactly we want to run on these services build, so we don't have to wait for 2 hours to deploy a small fix to an isolated service.
2 votes -
Allow destructive changes from Local File
Allow for the upload of a local file which includes the destructiveChangePost.xml, destructiveChange.xml, and destructiveChangePre.xml files to do destructive changes.
10 votes -
allow a method to set up default branches.
I frequently deploy from our on premises GitLab repo. It would be great to have the ability to set the default branch it goes to. It would be one less click for repetitive steps
5 votes -
Support package.xml filtering when using Git comparison with a SFDX folder structure
When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)
38 votes -
Display a custom name in Salesforce when deploying from Gearset
When we deploy a change to one of our Salesforce orgs using gearset, the name that is displayed in the "Deployment Status" in Salesforce is an ID. It would be helpful to display the name that we entered in Gearset instead of the ID so that we can easily identify the changes when looking at them in Salesforce
5 votesHi,
We have recently investigated adding this feature again, but unfortunately Salesforce still don’t seem to support being able to display custom names via the Api (or it’s a feature that’s not well documented). There are requests for adding this ability via:
https://success.salesforce.com/ideaView?id=08730000000cJdxAAE
If the situation changes then we’ll certainly revisit this. We’ll keep this post opened for other users to also add their votes but it’s currently out of our hands as to when or if it can be added.
Regards,
The Gearset Team
-
Include a feature to connect between SonarQube and Gearset
I really love using Gearset. It would be great if we have a plugin in there to integrate Gearset and SonarQube to display Static Code Analysis and Test Coverage in Sonar. I had tried this through CircleCI and it requires lot of configuration and we need write code to create and maintain the connection.
Whenever there is an update to the GIT Master it has to Initialize the Sonar Scanner and it'll run some tests and display results in SonarQube.
Thanks!11 votes -
Compare metadata by "Changed Date" for both "Source" and "Target"
In "Compare and Deploy", is there a way to add a column for "Changed Date" for the Source item, in addition to the Target item?
I want to select all the items which were more recently changed in the Source than in the Target. In my current large org compare-and-deploy, I see many items which are different but the one in the Target was more recently changed, so I don't want to overwrite that item in the Target.
7 votes -
Use the information in a JIRA ticket to select the components to deploy
Instead of manually selecting components to deploy. If we have an integration with JIRA and the components are listed on the JIRA ticket. Would it be possible to then specify JIRA tickets to deploy and have Gearset automatically build the deployment package?
2 votes -
Enhance the deployment history search functionality
When trying to gather packages together to combine them for a release, currently it is not possible to first limit by a text search then expand the date range (search hangs due to number of retrievals)
Could there be a way to enhance the history search to enable easier searching?
1 vote -
Export of the Comparison Results
My Suggestion: For our Customer i need to create a Documentation with all the Metadata Information from the Comparison. Even for Things which are not different.
A CSV Table would be great and a HTML Documentation would be awsome :)3 votes -
When viewing comparisons, allow the "Export All..." to utilize existing filters
When viewing a comparison... I have various filters set to exclude certain differences like "Reports, "Permission Sets". It would be nice if you provided an option on the "Export All..." page to either export everything (disregard filters) like it does now, or to respect any filters that currently exist on the comparison so that I only see the values shown on the page based on my filters.
1 vote -
Retain Link to JIRA Tasks When Combining Deployments
Part of our release management policy is for all deployment to be associated with JIRA tasks. I noticed that when cloning individual deployment the association with JIRA tasks is retained. However, when combining multiple deployments, the relationship with JIRA is broken and as a result, we need to re-associate each JIRA task back to the combined deployment package.
1 vote -
Allow retrying failed validations and deployments
I'm often running into the situation where the validation failed either due to transient circumstances in the org, or due to the org settings being incorrectly configured. In this scenario, I would like to simply retry the validation using the same package, and I'd look for that option somewhere here:
https://app.gearset.com/deployments/validations
Running a new comparison (using the "clone package" option) is unnecessary, takes a lot of time. Also using the "view comparison" option is overkill. I would rather not go through those motions of recalling the comparison results from cache, going through the analysis once again, etc. Because I know…
1 vote -
provide creation of immutable deployment package
I would like a way for Gearset to create an immutable deployment package that can then be deployed to different orgs. This immutable package should contain a copy of the selected objects, list of unit tests to be executed and not allow variation in the deployment except selecting the target org. This would also save time by not requiring a new comparison to run for each target org.
1 vote
- Don't see your idea?