-
Notifications
You must be signed in to change notification settings - Fork 466
fix: move custom fields to org settings #5163
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
Uffizzi Preview |
removes projectId Prop
c31aa56 to
bb04d70
Compare
Docker builds report
|
matthewelwell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me from a code perspective, but I wonder if there's a way that we can redirect any users that are expecting to navigate to the custom fields tab in the project settings to the organisation settings?
Sure thing! |
matthewelwell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now. I've added a small suggestion for the copy of the relocation warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and approved after committing suggestion 👏
Co-authored-by: Matthew Elwell <matthew.elwell@flagsmith.com>

Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
Ref: #4384
object_idneeds to be removed because when a field is set as required it's set at org level configuration, we don't need to specify the project idHow did you test this code?
Please describe.