-
Notifications
You must be signed in to change notification settings - Fork 887
Difficult to organize and display many templates #5492
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
Comments
One advantage to going with folders is an entire folder can have RBAC (e.g. |
Is this still important after we support multiple organizations? |
Sorry, missed your message. I'd say they serve different cases. |
We may solve this with a concept of projects under each organization. Each project will have independent templates/workspaces. |
Also related to #7318 in case when a user has too many templates. |
I think we should solve #7318 before we add pinning, folders or tags. Sorting and searching across our core views is table-stakes. |
This is not at the scale of our other roadmap items, so I am removing the label. |
If a developer is in a large organization and has access to 25+ templates, it would be difficult to find which templates are relevant to them in a long list.
Just because a developer has access to 25+ templates doesn't necessarily mean they should all be shown to them, as it's possible only 1-2 relevant to their use case. I have also wanted to hide/group templates from other users when I'm still iterating on them.
Some ideas:
/templates
(group:any(mine), os:fullstack
)The text was updated successfully, but these errors were encountered: