[ENG-9769] Metadata Tab Incorrectly Requires Optional Fields for Submission #789
+1
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ibutor and contributors may not load syncronically after step change
nsemets
approved these changes
Nov 24, 2025
mkovalua
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
In production, the Metadata tab for new registration drafts requires all fields to be filled before users can submit. Optional fields — including tags/keywords — are being treated as required, causing the tab to remain incomplete and blocking draft submission. This affects all providers, with immediate impact on Lifecycle and Global Flourishing Study, who expect a surge of submissions soon.
Summary of Changes
avoid check because registration will have always at least one contributor and contributors may not load syncronically after step change
Screenshot(s)
3727-df37-4d3b-9a51-022cdb31dfc3.mp4
Side Effects
The issue root, if there is a way to keep the contributors on step change it will be better solution than currently proposed solution, have not found the way how to succeed with such an approach from my side.
c241-1854-4bab-a8b3-2addc51f93e2.mp4
QA Notes