#2574767-36: Views listing page displays too few items on a page →
removed the "Tags" column from the list of views at /admin/structure/views, because it was rarely used.
I don't personally use Views Tags on every project, so I understand with, and largely agree with the reasoning in that issue. Also I couldn't find any other issues asking for it to be re-added, which probably also indicates that the feature is not used that often.
That being said, I do find Views tags very useful in specific situations, e.g.: for managing technical debt on a site with multiple developers and a tight timeline... I tag views by their base table, contextual filters, whether they use aggregation, and where they are used; so that it is easy for developers to find an existing view they can add a new display to (rather than creating an entirely new view), and it is easy to see which views could be combined when they are already a mess.
Ideally, the list of views at /admin/structure/views would become a view of its own (e.g.: as part of
#1823450: [Meta] Convert core listings to Views →
), which would allow me to simply add a tags column on the sites that required it; and leave it at the default everywhere else.
However, in the meantime, it would be handy to have a patch to apply to add the tags column back.
Write a patch to re-add the tags column.
I'll leave it to others to determine whether this is something we want to add back to Drupal core; or just leave here for people to apply when they need it.
Adds a "tags" column between Description and Displays to the list of views at /admin/structure/views
None.
None.
Needs work
11.0 🔥
Last updated
Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Re-rolled patch to work with current Drupal 10, which uses "stable9" instead of "stable" for the base theme.
Can this be re-rolled against 11.x-dev? The last attempt was 7 months ago against core 10.x.
Re-rolled patch against 11.x-dev. Please review