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.
294 results found
-
Share a deployment with a different team
If I use my Gearset instance to deploy for a client, I wanted to share the deployment history visibility with the client's Gearset team.
1 vote -
Allow for CSV to be extracted data type from completed deployment screen
Allow for CSV to be extracted data type from the completed deployment screen
1 vote -
Download Salesforce customer master data changes for a custom time period in a single file
We get a request from auditors every year. They want to see the customer master data changes for a specific month or time period. The customer master data objects like account, opportunity, contact, lead, etc.
I have a full Salesforce data backup job that runs once per day. If i start downloading the files for each day, it is gonna take a lot of time.
Therefore, I need one export for the whole month for customer master data objects like account, opportunity, contact, lead, etc.
1 vote -
Write deployment results to a custom Object.
We use a custom ticket object in our processes to track salesforce change requests. The ability to write deployment, validation results to a custom object would be very helpful.
1 vote -
The Ability to add deployments to a folder or tagging them...
On the Validated packages, Draft Deployments, Depolyment history it would be great if users could create folders or tags to group deployment or validated packages. Use case: Team has a large deployment that will be split into multiple parts a folder or tagging would help with organization and tracking.
1 vote -
The destructiveChangesPost.xml file should be processed in manual comparison
The destructiveChangesPost.xml should be processed when using local file as a source for manual comparison. Ideally the items listed in the destructive file should be used as filter for which to show in the Deleted filter
1 vote -
Allow Dev Updates to be Qued
Allow dev updates to be in a que so that you dont run into the problem of updating to many at the same time.
1 vote -
Update all Dev's button
Create a Update All Dev Sandbox button in a pipeline that allows you to quickly update all of the devs at once instead of clicking into each one.
1 vote -
Allow for different pull request messages.
I would like the ability to have different pull requests message per pull request that is autogenerated when you move through the pipeline.
Example: When I first create a pull request from dev to my next static environment the message would only pertain to that static environment. So from Dev to UAT I would include a pull request message pertaining to testing.
Then after that I would move from UAT to Staging so the message would be something about the testing and how it is complete and ready to move to staging which is our integration environment.
Then when that…
1 vote -
Update Slack notification messages format
Update the slack messages to more clearly define what happened in the action.
There should be a more clear title to the slack message. It should define what item was doing what. Currently that is grouped into a description which does not show on slack notifications.
CI job notifications should have a more clear "from where to where" section in the notification. Currently its grouped into the description.
1 vote -
All available branches display
Create a view that displays all active and available branches and there current commits and pull requests. That way if there a multiple branches per environment a release manager can see everything that is going on instead of having to click into each environment in the pipeline or going into git.
1 vote -
Show Auto resolved conflicts
When in the conflict resolution screen it would be nice to quickly see all files that have been auto resolved. Maybe with a icon of some sort on the left hand side next to the circle icon for resolved or not resolved.
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 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 -
Pre-fill Pull Request Description with comments from last commits
In order to save time, when a Pull Request is created from the Pipeline, the Description field could be pre-filled with the comments from the last commits in the feature branch, instead of forcing the User to type something.
1 vote -
Save sort order of grids
It would be nice to be able to sort by column names and save that sort order for the next time the page loads or save a default sort order. We sort often by jobname and would like to not have to resort everytime we need to touch a ci job to sort the column.
1 vote -
Is it possible to get an additional field in the compact view of the jira ticket ?
Is it possible to get an additional field in the compact view of the Jira ticket ? We would like to add Fix Version as well as what already exists.
1 vote -
Visibility to Log Files for Connections and Compare & Deploy Events
When you either make connections to 3rd party applications or run a Compare & Deploy, there is no visibility to the log files, I feel these should be accessible to the user so that we can understand the reason why something is failing and not have to have someone provide this information. Additionally it should have options to change the level of logging to provide detailed information when needed
1 vote -
User Data & Logs
For audit reason we have been asked to provide a comprehensive user list with the following data:
User Status (Active/Inactive)
User Creation/Removal Date
Created/Removed/Updated by
Updated Value (if you change the role of a user from member to owner or opposite)
User Last Login DateThese data are part of the user audit control (create/update/remove users) and are very important to prove you have control who gets access, and there is no risk for unauthorized access but also to prove that segregation of duties is in place.
Thank you!
1 vote -
Show PR Flow changes in Flow Navigator View
New new Flow Navigator view is really good.
It is such a shame that I am only able to view flow in flow navigator in comparison view (when creating pull request).
I would love to be able to open flow in flow navigator directly from teammates open pull requests. That would really speed up reviewing flow changes cuz reading metadata on VCS is not the clearest thing to do.1 vote
- Don't see your idea?