-
Notifications
You must be signed in to change notification settings - Fork 413
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
Reimplement input mirroring for OT milestone fields #3173
Comments
Hello @DanielRyanSmith, I am interested in assisting with this issue. I am understanding this request as adding the functionality to mirror OT milestone field values back into other input fields in the stage edit page in a way that is functional with the new implementation of form submission and tracking "touched" fields, is that the full scope of this issue? Please let me know if you have any other requests/desired functionality or any perspective that I might be missing to begin tackling this issue. |
Hi @GabriellaMSanchez - yes, feel free to take a shot at this issue. 🙂 The basic premise we are looking for is this:
This will likely require special logic for the |
@DanielRyanSmith Awesome, I'll reach out if there is anything additional. Thanks for the response! |
Hey @DanielRyanSmith ! Hope you're doing well.. Could you please tell me if this issue is still open as I am interested in assisting with this issue. |
Hi @DanielRyanSmith I have some doubts:
|
Hey @DanielRyanSmith , I see codebase migrated before last PR changes could be published. Thanks, |
hi @DanielRyanSmith , I’d love to work on this, can I take it if it's still open? |
hi i would like to work on this issue if its available |
hello, I would like to work on this issue if its available |
After #3162 has landed, the OT milestone fields on the stage edit page will no longer mirror their input into the other start and end fields if there is no existing value in those inputs. A special handler will need to be created to reimplement this input mirroring in a way that designates the other input fields as "touched" for form submission.
The text was updated successfully, but these errors were encountered: