Skip to content
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

[DOCS] Notify assignees when assigned to a case #147713

Merged
merged 5 commits into from
Jan 4, 2023

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Dec 16, 2022

Summary

Relates to #140743, #142307

This PR adds a section to https://www.elastic.co/guide/en/kibana/master/manage-cases.html that describes how to set up email notifications for cases.

When #147660 is merged, we can add a link for the notifications.connectors.default.email setting.

@github-actions
Copy link

Documentation preview:

@lcawl lcawl added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) docs Feature:Cases Cases feature v8.7.0 v8.6.1 release_note:skip Skip the PR/issue when compiling release notes labels Dec 17, 2022
@lcawl lcawl requested a review from a team December 17, 2022 00:35
@lcawl lcawl marked this pull request as ready for review December 17, 2022 00:35
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@lcawl lcawl enabled auto-merge (squash) December 17, 2022 06:16
@lcawl lcawl merged commit 1528c6a into elastic:main Jan 4, 2023
@lcawl lcawl deleted the case-notifications2 branch January 4, 2023 17:51
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jan 4, 2023
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.6

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Jan 4, 2023
)

# Backport

This will backport the following commits from `main` to `8.6`:
- [[DOCS] Notify assignees when assigned to a case
(#147713)](#147713)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-01-04T17:50:54Z","message":"[DOCS]
Notify assignees when assigned to a case
(#147713)","sha":"1528c6a6f98f05d17132b77971a1929684164f9f","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","v8.7.0","v8.6.1"],"number":147713,"url":"https://github.com/elastic/kibana/pull/147713","mergeCommit":{"message":"[DOCS]
Notify assignees when assigned to a case
(#147713)","sha":"1528c6a6f98f05d17132b77971a1929684164f9f"}},"sourceBranch":"main","suggestedTargetBranches":["8.6"],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/147713","number":147713,"mergeCommit":{"message":"[DOCS]
Notify assignees when assigned to a case
(#147713)","sha":"1528c6a6f98f05d17132b77971a1929684164f9f"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
@milanage
Copy link

As per #144391, there is an implication that you're not getting notified if you assign yourself to the case. Might be better to make it explicit in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Feature:Cases Cases feature release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.6.0 v8.6.1 v8.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants