-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Epic] Troubleshooting Runbook #18171
Comments
gracekretschmer-metrostar
added
Needs refining
Issue status
CMS Team
CMS Product team that manages both editor exp and devops
labels
May 20, 2024
24 tasks
8 tasks
gracekretschmer-metrostar
changed the title
Troubleshooting Drupal Runbook
[Epic] Troubleshooting Drupal Runbook
May 21, 2024
gracekretschmer-metrostar
changed the title
[Epic] Troubleshooting Drupal Runbook
[Epic] Troubleshooting Runbook
May 21, 2024
22 tasks
gracekretschmer-metrostar
assigned michelle-dooley and gracekretschmer-metrostar and unassigned timcosgrove and edmund-dunn
Jun 5, 2024
26 tasks
24 tasks
30 tasks
We are going to pause this work until the developer support discovery (#18446) is completed. |
Idea: refine this ticket to fold into the platform support work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story or Problem Statement
As a new developer working within Drupal CMS, I need to understand how to navigate the CMS environments and troubleshoot and, if needed, escalate errors in my code.
Description or Additional Context
To better onboard developers working within Drupal CMS, the CMS team is going to work on a troubleshooting runbook to support developers and provide better guidance to when and how to reach out to the CMS team for support. For the first iteration of this runbook, we will be focusing on three areas:
Acceptance Criteria
Tasks
The text was updated successfully, but these errors were encountered: