Update fme-support.md with correct in Harness app steps #11527
+9
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://68c0ddcd2443c78314ba79c0--harness-developer.netlify.app |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
Here are the actual steps if you are "already on the Harness platform"
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: