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

[Task] When you try to add a participant, the message remains blocked. #9752

Open
NiQuintin opened this issue Jan 29, 2025 · 1 comment · May be fixed by #9755
Open

[Task] When you try to add a participant, the message remains blocked. #9752

NiQuintin opened this issue Jan 29, 2025 · 1 comment · May be fixed by #9755
Assignees
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature
Milestone

Comments

@NiQuintin
Copy link

Description

When you try to add a participant in a task, the message remains blocked.

Environment

  1. OpenCTI version: 6.4.9

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. adding a participant in a task

Expected Output

Participant added

Actual Output

Nothing happen and when coming back on the little window it's still blocked

Additional information

Reproduced in testing.

Screenshots (optional)

Image

@NiQuintin NiQuintin added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 29, 2025
@romain-filigran
Copy link
Member

Reproduced in latest 6.4.9 (rolling) version. Browser stacktrace:

4front-OB5JQZM2.js:69836 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'map')
    at S (front-OB5JQZM2.js:69836:19129)
    at front-OB5JQZM2.js:427:33247
    at front-OB5JQZM2.js:427:36840
    at front-OB5JQZM2.js:427:32486

@romain-filigran romain-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 29, 2025
@romain-filigran romain-filigran added this to the Bugs backlog milestone Jan 29, 2025
@romain-filigran romain-filigran added the regression Label to identify the bug as a regression of previously working feature label Jan 29, 2025
@Kedae Kedae self-assigned this Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants