Conversation
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| - **Helm CLI**: Issues with direct Helm installs and the Replicated SDK microservice | ||
| - **Native Scheduler**: Issues with the legacy Replicated Native Scheduler | ||
|
|
||
| 1. On the self-service page, review the suggested community articles and documentation links to see if your question has already been answered. If you still need help, click **Open a support request**. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('been answered').
| You can also click **Make a feature request** to submit a feature request instead. Feature requests collect a title, problem description, and an optional proposed solution. | ||
|
|
||
| 1. In section 1 of the support request form, complete the required fields that apply to all requests: | ||
| If your team has a collab repository configured, you can also click **View open issues and requests** to see all submitted issues and feature requests on GitHub. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
| You can also click **Make a feature request** to submit a feature request instead. Feature requests collect a title, problem description, and an optional proposed solution. | ||
|
|
||
| 1. In section 1 of the support request form, complete the required fields that apply to all requests: | ||
| If your team has a collab repository configured, you can also click **View open issues and requests** to see all submitted issues and feature requests on GitHub. |
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'collab'?
| If your team has a collab repository configured, you can also click **View open issues and requests** to see all submitted issues and feature requests on GitHub. | ||
| ::: | ||
|
|
||
| 1. (KOTS, Embedded Cluster, and kURL only) Upload one or more support bundles. The support bundle metadata is used to pre-populate customer information in the request form. |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('is used').
| <td>Enter your first and last name.</td> | ||
| <th>First Name, Last Name, and GitHub Username</th> | ||
| <td> | ||
| <p>These fields are only displayed if your Vendor Portal account does not have a GitHub username configured. Your GitHub username is required to access the GitHub collab repo used for support tickets.</p> |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('is required').
| </tr> | ||
| <tr> | ||
| <th>Is the issue with installing an application?</th> | ||
| <th>Has this been reproduced in a different installation/environment?</th> |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('been reproduced').
| <li><strong>New install:</strong> The issue is with a first time installation</li> | ||
| <li><strong>Existing instance:</strong> The issue is with an instance after an initial successful installation, including upgrades.</li> | ||
| </ul> | ||
| <p>Indicates whether the issue has been confirmed in more than one environment. If the issue is both blocking production and reproducible, the request may be escalated to Severity 1.</p> |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('been confirmed').
| <li><strong>New install:</strong> The issue is with a first time installation</li> | ||
| <li><strong>Existing instance:</strong> The issue is with an instance after an initial successful installation, including upgrades.</li> | ||
| </ul> | ||
| <p>Indicates whether the issue has been confirmed in more than one environment. If the issue is both blocking production and reproducible, the request may be escalated to Severity 1.</p> |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('be escalated').
| 1. In section 2, attach one or more support bundles: | ||
| - Use your pre-selected support bundle or select a different bundle in the pick list | ||
| - Select **Upload and attach a new support bundle** and attach a bundle from your file browser | ||
| If the severity calculation results in a Severity 1 (critical) issue, a confirmation dialog is displayed warning that an on-call engineer will be paged. You can choose to: |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('is displayed').
| 1. In section 2, attach one or more support bundles: | ||
| - Use your pre-selected support bundle or select a different bundle in the pick list | ||
| - Select **Upload and attach a new support bundle** and attach a bundle from your file browser | ||
| If the severity calculation results in a Severity 1 (critical) issue, a confirmation dialog is displayed warning that an on-call engineer will be paged. You can choose to: |
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('be paged').
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 participants
Docs update for the new support form https://vendor.replicated.com/support