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.
164 results found
-
Access to Jira custom fields
we have a custom field we use that ties to a release number. It would be great if as an additional option to selecting tickets, access this field, set the value (in this case our release number) and have gearset pull all related requests in.
5 votes -
Create a VSTS Build Task for Gearset
VSTS offers the ability to create build definitions to validate/deploy your code, but Gearset customers don't have much options natively in VSTS to trigger a Gearset deployment. We can scan a code repository for changes every 4 hours in order to do a CI deployment-- but that's about it.
VSTS offers the ability for vendors to create "Build Tasks" for their applications, where you can initiate a VSTS build and get results. This is basically a controlled version of API access to the tool.
More information:
VSTS Marketplace - https://marketplace.visualstudio.com/vsts
VSTS "Add a Build Task" - https://www.visualstudio.com/en-us/docs/integrate/extensions/develop/add-build-taskIt would be…
2 votes -
Support customer S3 buckets for storage
Allowing customers to specify their own S3 buckets for storage could be beneficial for the product. This would give the customer enhanced security and control over their data.
1 vote -
Display org authorisation errors
When I link my Salesforce org with Gearset, I like to use OAuth as that provides the best security.
Whenever there is an error during the linking process, such as when:
- The app is blocked (OAUTHAPPBLOCKED)
- I press Deny on the OAuth consent screen
- The org has IP restrictions in place that prevents Gearset from completing the OAuth flow
Gearset returns to the Manage Orgs or Configure page without showing me what went wrong!
1 vote
- Don't see your idea?