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

[Feature Request]: custom fieldset as default #11269

Open
fggec opened this issue Jun 7, 2022 · 3 comments
Open

[Feature Request]: custom fieldset as default #11269

fggec opened this issue Jun 7, 2022 · 3 comments

Comments

@fggec
Copy link

fggec commented Jun 7, 2022

Is your feature request related to a problem? Please describe.

No

Describe the solution you'd like

We would like to have the opportunity to define the custom fieldset as default for all new asset models. Currently we have to set it manually if we create a new model.

Describe alternatives you've considered

Do it manually for all new created models.

Additional context

No response

@fggec fggec changed the title [Feature Request]: [Feature Request]: custom fieldset as default Jun 7, 2022
@snipe
Copy link
Owner

snipe commented Jun 7, 2022

Since we have bulk asset model editing, I'm not sure this is super high priority, but... @Godmartinz - want to take a stab at this? One field added to models table for default value. We can chat offline.

@brunapinos
Copy link

I'm having the same problem in my company, where sometimes people forget to select the Add default values checkbox.
One solution I think would solve the problem is to change the behavior to always shows the default and the checkbox would be Remove default values.

I'll be happy to open a pull request with this change.

@NPGH0
Copy link

NPGH0 commented Dec 19, 2023

+1 from my site also
we use FMCS and there are fields which are always required. therefore we have a "default"/"basic" fieldset which is the bare minimum of custom fields which should be added to an asset. And sometimes it gets forgotten to add the fieldset :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants