-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[CaseM] update jira/snow syncing docs #26465
Conversation
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also appear in the hack doc imo.
It's not scalable that for each case type added that doesn't allow jira bysinc we need to update this doc. We should find a better way to make customers aware of it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making these updates! Left some suggestions, let me know if you have any questions!
content/en/service_management/case_management/create_notifications_and_third_party_tickets.md
Outdated
Show resolved
Hide resolved
content/en/service_management/case_management/create_notifications_and_third_party_tickets.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Esther Kim <[email protected]>
/merge |
Devflow running:
|
What does this PR do? What is the motivation?
Updates the docs to reflect limitations for Change Management.
Merge instructions
Nothing specific, CHM is being turned on 11/24.
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment:Additional notes