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]: Default view in Asset Models according to assigned fieldset #14053

Open
NPGH0 opened this issue Dec 19, 2023 · 4 comments
Open

Comments

@NPGH0
Copy link

NPGH0 commented Dec 19, 2023

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

No, not a Problem, more a QoL Feature

Describe the solution you'd like

if we go to Settings-->Asset Models --> and choose an asset model, the default visible columns should also contain the fields which are added by the assigned fieldset.
Also it should only show those columns which actually have information and remove blanc ones.
This would lead to a better user experience since all needed information are displayed on demand and we do not have to reorganize the columns everytime we move between asset models or other asset views.

Describe alternatives you've considered

No response

Additional context

No response

Copy link

welcome bot commented Dec 19, 2023

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented Dec 20, 2023

I don't really understand the ask - can you clarify? Do you mean the list view when you select an asset model?

@NPGH0
Copy link
Author

NPGH0 commented Dec 20, 2023

Yes exactly, the list view for an asset model :)

I think it would make more sense that if you have added a fieldset to an asset model, that this fieldset is also automatically displayed (the custom fields which have been added) when you view the asset model.

@snipe
Copy link
Owner

snipe commented Dec 20, 2023

It does make sense, it's just pretty clunky to get there because of how our presenters are set up. (The presenters determine which columns to provide on different views.) We could make a separate one for asset listings on models, but it seems duplicative, and will surely be missed in some other update down the line. Let me think on this a bit.

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

No branches or pull requests

2 participants