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

Airlock incorrectly assigns latest update user to initiator of request #2765

Closed
jjgriff93 opened this issue Oct 20, 2022 · 0 comments · Fixed by #2779
Closed

Airlock incorrectly assigns latest update user to initiator of request #2765

jjgriff93 opened this issue Oct 20, 2022 · 0 comments · Fixed by #2779
Assignees
Labels
airlock bug Something isn't working

Comments

@jjgriff93
Copy link
Collaborator

When an airlock request is updated, the creator_user_id field is overwritten with the user that's just updated the request. This field should be untouched by subsequent updates after creation.

Steps to reproduce

  1. Create an airlock request in draft
  2. Sign in as a different user with appropriate permissions and submit the draft request
  3. It will change the initiator to the latter user
@jjgriff93 jjgriff93 added bug Something isn't working airlock labels Oct 20, 2022
@jjgriff93 jjgriff93 moved this to Backlog in AzureTRE - Crew Rock Oct 20, 2022
@jjgriff93 jjgriff93 moved this from Backlog to In Progress in AzureTRE - Crew Rock Oct 20, 2022
@jjgriff93 jjgriff93 changed the title Airlock incorrectly assigned latest update user to initiator of request Airlock incorrectly assigns latest update user to initiator of request Oct 20, 2022
@jjgriff93 jjgriff93 self-assigned this Oct 21, 2022
@jjgriff93 jjgriff93 moved this from In Progress to PR in AzureTRE - Crew Rock Oct 24, 2022
Repository owner moved this from PR to Done in AzureTRE - Crew Rock Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
airlock bug Something isn't working
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant