From bccf5b0c8a330fc657b8056ff52ed67a3c048851 Mon Sep 17 00:00:00 2001 From: Dave Karow Date: Tue, 9 Sep 2025 18:57:09 -0700 Subject: [PATCH] Update fme-support.md with correct in Harness app steps Better to teach users how to log support cases from within the app then sending them to the zendesk portal, which requires them to log in via the app first anyway. I could be wrong here... might be that the SSO via app to get them into Zendesk could work when their account access has an issue, but it struck me as odd that the instructions were not to the in-app experience. --- .../fme-support.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/feature-management-experimentation/fme-support.md b/docs/feature-management-experimentation/fme-support.md index 56402339ac4..304dd653f3c 100644 --- a/docs/feature-management-experimentation/fme-support.md +++ b/docs/feature-management-experimentation/fme-support.md @@ -25,13 +25,14 @@ If you are already on the Harness platform, you can create a Harness Zendesk Sup To create a support ticket: -1. Go to [https://support.harness.io](https://support.harness.io) -2. Log in and Click on Submit a Request -3. Enter a meaningful subject -4. Provide steps to reproduce the issue in the description field -5. Select the priority level -6. Attach any relevant screenshots or mini video clips -7. Submit the ticket +1. Click "Help" in the Harness left navigation +2. Click "Submit a ticket" in the dialog that appears +3. Enter a meaningful subject and click "Continue" +4. Select the priority level +5. Choose "Feature Management & Experimentation" from the module menu +6. Provide steps to reproduce the issue in the description field +7. Attach any relevant screenshots or mini video clips +8. Submit the ticket This will create an internal Zendesk ticket, which is actively monitored. @@ -59,3 +60,4 @@ And that’s it! The product management team will triage these submitted ideas, ask questions if needed, allow all users interested in participating in the conversation, and provide updates on the progress and ETA. Users will automatically be notified on each change of tickets that they are subscribed to (either voted on or created the feature request). --> +