Plan requirement
| Subscription | Suite Enterprise or higher, Support Enterprise |
| Access | Admin |
Keeping a record of what was deployed and when. The thing you want when something behaves oddly next month.
Review them
- Open Admin Center, then Account, then Sandbox, then Deployments.
- Read what was deployed, by whom and when.
- Compare against when the behaviour changed.
The question it answers
"Something started going wrong around the eleventh." The deployment history either names the change or rules it out, and both are progress.
Without it, that question turns into reading every trigger.
Record the why separately
The history shows what changed. It does not say what problem you were solving or who asked, and that is what the next person needs.
One line per deployment, wherever your team keeps notes.
One change at a time
Three deployments in an afternoon means you cannot attribute an effect to any of them. Slower is genuinely faster once something is wrong.
Read it after any incident
Before investigating anything else, look at what was deployed recently. A surprising share of "Zendesk is behaving strangely" is a change somebody made and did not mention.
Watch who deploys
If several people deploy independently, the history is also how you notice two changes that conflict. Worth a look before you add a third.
Comments
0 comments
Article is closed for comments.