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

Creator changed when accessing an Analyst workbench #6048

Closed
yassine-ouaamou opened this issue Feb 20, 2024 · 0 comments · Fixed by #6180
Closed

Creator changed when accessing an Analyst workbench #6048

yassine-ouaamou opened this issue Feb 20, 2024 · 0 comments · Fixed by #6180
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@yassine-ouaamou
Copy link
Member

Description

When a user A accesses an analyst workbench created by a user B. The creator of workbench is changed to User B.

Environment

Testing/Demo

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to Data > Import
  2. Find an analyst workbench created by a different user
  3. Access it and then go back to Data > Import

Expected Output

The creator of the analyst workbench should not be changed

Actual Output

The creator of the analyst workbench is the logged user now

@yassine-ouaamou yassine-ouaamou added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 20, 2024
@jborozco jborozco added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Feb 20, 2024
@nino-filigran nino-filigran removed the critical use to identify critical bug to fix ASAP label Feb 20, 2024
@nino-filigran nino-filigran added this to the Release 6.0.1 milestone Feb 20, 2024
@marieflorescontact marieflorescontact self-assigned this Feb 20, 2024
@Jipegien Jipegien modified the milestones: Release 6.0.1, Release 6.0.2 Feb 29, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 1, 2024
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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants