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

[DUOS-2640][risk=no] Ensure DAC Id is Submitted on Study Update #2333

Merged
merged 1 commit into from
Sep 21, 2023

Conversation

rushtong
Copy link
Contributor

Addresses

https://broadworkbench.atlassian.net/browse/DUOS-2640

Summary

Minor bug fix - the dac id, even though selected, was filtered out of the submitted entity


Have you read Terra's Contributing Guide lately? If not, do that first.

  • Label PR with a Jira ticket number and include a link to the ticket
  • Label PR with a security risk modifier [no, low, medium, high]
  • PR describes scope of changes
  • Get a minimum of one thumbs worth of review, preferably two if enough team members are available
  • Get PO sign-off for all non-trivial UI or workflow changes
  • Verify all tests go green
  • Test this change deployed correctly and works on dev environment after deployment

@rushtong rushtong requested a review from a team as a code owner September 19, 2023 21:50
@rushtong rushtong changed the title [DUOS-2640][risk=no] Ensure DAC Id is submitted [DUOS-2640][risk=no] Ensure DAC Id is Submitted on Study Update Sep 19, 2023
@rushtong rushtong merged commit ce3ea85 into develop Sep 21, 2023
@rushtong rushtong deleted the gr-DUOS-2640-save-study-bug branch September 21, 2023 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants