David S
My feedback
19 results found
-
33 votesDavid S
supported this idea
·
-
2 votesDavid S
supported this idea
·
-
1 voteDavid S
shared this idea
·
-
40 votesDavid S
supported this idea
·
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →David S
supported this idea
·
-
2 votesDavid S
shared this idea
·
-
4 votesDavid S
shared this idea
·
-
4 votesDavid S
supported this idea
·
-
16 votesDavid S
supported this idea
·
-
12 votes
If we implemented this and it was only able to search metadata from that point in time onwards, would that be useful or would it be confusing to communicate in the UI?
David S
supported this idea
·
-
8 votes
Thanks for the suggestion.
When you run a deployment, the deployment success email contains the PDF of the deployment report, as well as a link to your deployment history to view the full information.
For the test/change monitoring emails, what sort of report would you like to see? Would you like to see the full information on tests run or just a summary of key stats?
We don’t currently provide the ability to export PDF reports for our change and test monitoring jobs in the same way as our deployments, but it’s something we’ve been thinking about putting in.
Thanks,
Jason.An error occurred while saving the comment David S
supported this idea
·
-
11 votesDavid S
supported this idea
·
-
11 votesDavid S
supported this idea
·
-
12 votesDavid S
supported this idea
·
-
16 votesDavid S
supported this idea
·
-
8 votesDavid S
supported this idea
·
-
20 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →David S
supported this idea
·
-
105 votes
Hello. A large number of commenters requested the ability to carry out value replacements as part of metadata deployments.
Gearset now offers a feature called Environment Variables that lets you do just that!
It works with both manual and CI deployments and lets you target either a Salesforce org or a Git repo of your choice. And, for a number of key metadata types, you can even specify the exact 'field' where the replacement should take place.
If you have any feedback on the Environment Variables feature, please open a new feature request or simply let us know in the in-app chat.
Thank you for upvoting this feature request and we hope that you will find the Environment Variables feature useful.
Blog post: https://gearset.com/blog/environment-variables/
Support doc: https://docs.gearset.com/en/articles/5557015-using-environment-variables-in-gearset
David S
supported this idea
·
-
29 votesDavid S
supported this idea
·
For change monitoring we need to have the PDF which the details of metadata.
One usage for the change monitoring is to track metadata change on production and especially the change not made by the IT team. So in this case just to be informed that metadata are change has no sense you need to know which metadata are changed in order to identify if it's normal (report / list view can be authorized) or critical (like permissions automatically change by Salesforce during the huge bug of last week).
Regards