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.

Sign up for GitHub

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

Jump to bottom

[Security Solution]: Change status dropdown gets stuck under cases tab if user click multiple times. #141381

Closed
ghost opened this issue Sep 22, 2022 · 7 comments
Closed

[Security Solution]: Change status dropdown gets stuck under cases tab if user click multiple times. #141381

ghost opened this issue Sep 22, 2022 · 7 comments
Assignees
@cnasikas
Labels
bug Fixes for quality problems that affect the customer experience Feature:Cases Cases feature good first issue low hanging fruit impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed

Comments

@ghost
Copy link

ghost commented Sep 22, 2022

Describe the bug:
Change status dropdown gets stuck under cases tab if user click multiple times.

Build Details:

VERSION: 8.5.0-SNAPSHOT
BUILD: 56489
COMMIT: ac5064b771f6edc2a2ea71da9f68e1afcd08a539

Preconditions

  1. Kibana should be running.
  2. Cases should be available.

Steps to Reproduce

  1. Navigate to Cases tab.
  2. Now, under status column click on change status dropdown.
  3. Under change status dropdown click twice on any of the status.
  4. Observe that change status dropdown gets stuck under cases tab if user click multiple times.

Actual Result
Change status dropdown gets stuck under cases tab if user click multiple times.

Expected Result
Change status dropdown should not get stuck under cases tab if user click multiple times.

Screen-Recording:

Cases.-.Kibana.-.Google.Chrome.2022-09-22.16-32-09.mp4
@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.5.0 labels Sep 22, 2022
@ghost ghost self-assigned this Sep 22, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@ghost ghost assigned MadameSheema and unassigned ghost Sep 22, 2022
@MadameSheema MadameSheema removed their assignment Sep 22, 2022
@MadameSheema MadameSheema added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Sep 22, 2022
@elasticmachine
Copy link
Contributor

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

@MadameSheema MadameSheema added the Feature:Cases Cases feature label Sep 22, 2022
@elasticmachine
Copy link
Contributor

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

@jonathan-buttner jonathan-buttner added good first issue low hanging fruit impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. v8.5.0 labels Sep 22, 2022
@rutviklhase
Copy link

Hey! Would love to take this up.

@rutviklhase
Copy link

I'm doing this as a Hacktoberfest participant and this issue didn't seem to have the tag. Do issues without the Hacktoberfest count?
Thanks!

@cnasikas
Copy link
Member

cnasikas commented Oct 3, 2022

Hey! We plan to remove the ability to update the status from the dropdown and introduce row actions. The fix cannot be merged in the main branch. I would suggest working on something else to avoid unnecessary work. Thanks!

@cnasikas
Copy link
Member

This PR #142150 fixed the issue. We introduce new bulk & and row actions and we removed the ability to change the status from the table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cnasikas cnasikas

Labels
bug Fixes for quality problems that affect the customer experience Feature:Cases Cases feature good first issue low hanging fruit impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) triage_needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cnasikas @elasticmachine @MadameSheema @jonathan-buttner @rutviklhase