Draft: Blog Post: Add automation to your Service Desk project using gitlab-triage

Closes Blog Post: Add automation to your Service Desk ... (#34612)

Contributes to Explain how to set up automation with gitlab-tr... (gitlab-org/gitlab#425775)

Checklist for writer

• Link to issue added, and set to close when this MR is merged
• Due date and marketing milestone (e.g. Mktg: 2021-03-28) added to title for the desired publish date
• If time sensitive
  • Added ~"priority" label if blog needs to run in the next few days
  • Mentioned @sgittlen to give her a heads up ASAP
• Blog post file formatted correctly, including uploading and embedding in markdown any accompanying images
• All relevant frontmatter included
• Review app checked for any formatting issues
• Reviewed by fellow team member(s)
• Reviewer(s) marked approved before sending to blog team
  • Any required internal or external approval for this blog post has been granted (please leave a comment with details)
  • Reviews by Legal team if necessary according to SAFE guidelines
• Assign to @Sgittlen for final review

After the blog has been published:

• Share on your social media channels
  • Add ?utm_medium=social&utm_campaign=blog&utm_content=advocacy to the end of the blog URL when you share on social media, for data tracking. Your link should look like this:https://about.gitlab.com/blog/20xx/xx/xx/blog-title/?utm_medium=social&utm_campaign=blog&utm_content=advocacy
• After you've shared on your social media profiles, select one of the posts and link it in the #social_media_action Slack channel for everyone to engage with your post. The GitLab social team may engage or even share your social media post to amplify the work.
• To learn more about how to use your own social media channels for GitLab, check out our team member social media guidelines here.