Skip to content

Conversation

@nastasha-solomon
Copy link
Contributor

@nastasha-solomon nastasha-solomon commented Jun 16, 2022

Fixes #2065.

Preview:

@nastasha-solomon nastasha-solomon mentioned this pull request Jun 16, 2022
15 tasks
Copy link
Contributor

@benironside benironside left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, left one minor suggestion.

nastasha-solomon and others added 2 commits June 18, 2022 09:39
Co-authored-by: benironside <91905639+benironside@users.noreply.github.com>
Copy link
Contributor

@joepeeples joepeeples left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I added some totally optional suggestions for tightening up the paragraph.

Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
Copy link

@michaelolo24 michaelolo24 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 LGTM!

@nastasha-solomon nastasha-solomon added the readyforQA PRs that are ready for QA review. label Jun 22, 2022
Copy link
Contributor

@jmikell821 jmikell821 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks for merging in feedback :-) We'll wait for QA to do a final review.

@ghost
Copy link

ghost commented Jun 23, 2022

#2077

Hi @nastasha-solomon

we have validated this preview links for the respected changes and all changes are available and good to go.

Fixed Areas:

image

image

@ghost ghost removed the readyforQA PRs that are ready for QA review. label Jun 23, 2022
@ghost ghost added the QA:Validated Issue has been Validated by QA Team label Jun 23, 2022
@mergify
Copy link
Contributor

mergify bot commented Jun 24, 2022

This pull request is now in conflicts. Could you fix it @nastasha-solomon? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b issue-2065-alert-prev-time upstream/issue-2065-alert-prev-time
git merge upstream/main
git push upstream issue-2065-alert-prev-time

@nastasha-solomon nastasha-solomon merged commit 9da2d9d into main Jun 24, 2022
@nastasha-solomon nastasha-solomon deleted the issue-2065-alert-prev-time branch June 24, 2022 22:20
mergify bot pushed a commit that referenced this pull request Jun 24, 2022
…ce section (#2077)

Co-authored-by: benironside <91905639+benironside@users.noreply.github.com>
Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
(cherry picked from commit 9da2d9d)
nastasha-solomon added a commit that referenced this pull request Jun 24, 2022
…evalence section (backport #2077) (#2148)

Co-authored-by: benironside <91905639+benironside@users.noreply.github.com>
Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
Co-authored-by: nastasha-solomon <79124755+nastasha-solomon@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature: Alerts QA:Validated Issue has been Validated by QA Team Team: Docs Team: Threat Hunting Formerly Data Visibility v8.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DOCS] Add the "investigate in timeline" button to the alert prevalence section

7 participants