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

Activities. activity filter depth:-1 does not list activity #9850

Closed
Tracked by #9683
Salipa-Gurung opened this issue Aug 19, 2024 · 0 comments · Fixed by #10032
Closed
Tracked by #9683

Activities. activity filter depth:-1 does not list activity #9850

Salipa-Gurung opened this issue Aug 19, 2024 · 0 comments · Fixed by #10032
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug

Comments

@Salipa-Gurung
Copy link
Contributor

Salipa-Gurung commented Aug 19, 2024

Describe the bug

depth (default -1): include all subfolders of the given fileId if set to -1.

Activity is not listed in a KQL query when the activity filter depth is set to -1, even though it is -1 by default #9194.

Steps to reproduce

  1. Create folders:
    • New folder
    • New folder/Sub folder
    • New folder/Sub folder/test folder
curl https://host.docker.internal:9200/graph/v1beta1/extensions/org.libregraph/activities\?kql\=itemid:{itemid}+AND+depth:-1
-uadmin:admin \
-vk

Expected behavior

Expected to get all the activities of New folder including activities of its sub-folders.

Actual behavior

Response does not contain any activity.

{"value":[]}
@Salipa-Gurung Salipa-Gurung changed the title Activities. depth depth:-1 does not list activity Activities. activity filter depth:-1 does not list activity Aug 19, 2024
@tbsbdr tbsbdr added the Priority:p2-high Escalation, on top of current planning, release blocker label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants