Ability to Group Charts And Dashboards via Tags or Folders

[kevinpostlewaite]

Is your feature request related to a problem? Please describe.
It's difficult to find specific charts and dashboards that I've created.

Describe the solution you'd like
As a user, I would like to be able to logically group my charts and my dashboards. I would like either folders or to be able to filter by tags when accessing the list of charts and dashboards.

Additional context
This is a much requested feature with many closed issues:

• Allow users to tag dashboards from November, 2017
• Folder structure for dashboard and slice from December, 2017
• Organising Charts List from April, 2019
• Group Dashboards folders or tags from April, 2019
• Ability to Tag Charts for Easy Filtering

There's even a PR but it appears that it may need to be rewritten to be accepted:
Tagging frontend

[eugeniamz]

Did you see SIP-34.
A lot of changes in the UI are happening. Check there and add your comments

[kevinpostlewaite]

Thanks @eugeniamz! That proposal is really impressive and I look forward to seeing the results. There's a lot there and I may have missed something but I didn't see any impact on grouping charts/dashboards although it looks like search in general is improved. What I would like (and don't see in that proposal) is a way for me to put charts/dashboards for, say "Marketing" or "Finance" in one directory, or apply different tags, so that I can limit my search/list display appropriately. Even though Search is improved in that proposal I don't see a way to limit to a cross-cutting subset of my charts/dashboards. Maybe this could be done by artificially creating duplicates of underlying data references, one per discriminating category value, but that would be sub-optimal.

[eugeniamz]

Great feedback!! I will share this with Preset designers team.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[bkyryliuk]

+1 to the @kevinpostlewaite feature request.
This is smth we would love to see as well

[rubypollev]

+1, this is important to our team.

[isunix]

What @kevinpostlewaite said is really what we need now, folders to organize our dashboards

[junlincc]

🏷search

[junlincc]

We are exploring global search which will be able solve the problem you have -
It's difficult to find specific charts and dashboards that I've created. tag and folder certainly could be alternative solutions. we would love to hear more about the use cases from you. @kevinpostlewaite @isunix @rubypollev @betodealmeida

[rubypollev]

Tags more useful at this time than folders, but folders would be great. Many tags to one chart / query for analytics approved queries, OKR queries, marketing-related / product-related queries, etc. would be soo helpful.

[chuancyzhang]

+1

[EBoisseauSierra]

@junlinc Having directories would help “dashboard consumers” to easily find/explore available dashboards. This way has — imho — a few advantages over tags:

1. Directories can be nested (what has pros and cons compared to multiple same-level-tags).
2. It's “push” rather than “pull” exploration: users are shown the various directories they can access, rather than having to guess what it the right tag to search for (is it “finance”, “finances”, “financial”, “revenue”, …?).
3. At start (blank search), you're not overwhelmed with all the dashboards you have access to; you're shown the top-level directories instead.

That's how Metabase does it and our novice users have found it — except the fact they confusingly call directories “collections” — quite convenient.

[shawnz42]

+1, this is important to our team.

[junlincc]

@EBoisseauSierra thanks for elaborating your business needs for folders/directories, and the pros and cons of different solutions. we were gonna implement global search for Superset 1.0 but the project has been reprioritized. it's good to know how other BI tools are solving content exploration challenge and how their solution is meeting your needs.
we should reconsider different options for content discoverability next year. @Steejay

[timoh]

👍 this our team is also bumping into so many dashboards. The search of course helps a bit, but the problem often is that the search only helps if you know what you're searching for.

Thus, having tags would be really helpful, as they can be used in all kinds of ways and are more flexible than folders, as you can form multiple parallel flexible hierarchies which folders do not enable. Github Issues' labels are a great example: you can have "categories of labels" just by using a colon, such as how this project uses them: enhancement:committed or enhancement:request

So in a similar way you could have for example: department:marketing and project:supersecretproject or whatever you like

[kevinpostlewaite]

This has been re-submitted as an issue:
#19398

[nikhil-kuyya-talentas]

Any thoughts on tagging approaches used for back-end and mimic the same approach of tagging feature ( which was closed) in front-end.
I am trying to understand these code for tagging for back-end and front-end( which is closed) can we try to implement in our private repo.

[hushaoqing]

+1

[katerina-glushko]

+1
We have several teams. They produce a lot of charts and dashboards all of which contain data about different business areas and so on. Now it's just a mess. Business users can't sort it all out and find dash/chart on their own.

[rubypollev]

I have a work-a-round. I created a directory dashboard filtering on a prefix... sort of acts like a folder.

Here's the simplified components:

• Organize your dashboard titles like so: <CATEGORY_NAME>: <DASHBOARD_NAME>
• Create a dataset on your Superset metadata database with this in the SELECT... it should also have any additional metadata on dashboards you need in your SELECT:

...
    CASE 
      WHEN dashboards.dashboard_title LIKE '%:%' THEN SPLIT_PART(d.dashboard_title, ':', 1)
      ELSE NULL 
      END AS dashboard_category
...

• Add a calculated column like so: CONCAT('<a href="https://<SUPERSET_ROOT>/superset/dashboard/', dashboard_id, '">', dashboard_title, '</a>') . I've named this Dashboard Title /w URL
• Create a table chart listing all dashboards SELECTing the URL column (and any other metadata).
• Create a dashboard with this chart and the prefix as a filter

Now you can filter your dashboards on a category, and navigate to them easily.

Not great, but it works.

[SergiGomez]

+100 from my side. We have dozens of dashboards and it's very inefficient to navigate through them on Superset. We have some workarounds too such as adding a prefix in the dashboard's name. It's such a basic feature, I don't understand why it's not been implemented yet??

[giovannipapini-agilelab]

Hi, are there any news about this feature?

[LeoDiep]

+1 is there any update on this cause we are needing it so desperately

[HeathLee]

+1 need this feature too

[Valenzione]

Hi, are there any news about this feature?

[maxbaldin]

+1

[mdeshmu]

frontend support for TAGGING_SYSTEM ff was merged recently via #20876 but It isn't released yet.

[svdimchenko]

@mdeshmu could you advice if TAGGING_SYSTEM will support tag-based security as well ? For instance, I want to have following dashboards structure:

• A with tags all, A
• B with tags all, B
  ...
  and I have roleAll, roleA, roleB with following accesses:
• roleAll - access to all dashboards
• roleA - access to dashboards with tag A only
• roleB - access to dashboards with tag B only

[mdeshmu]

@dpgaspar might be able to answer this.

[tanmaykansara]

+1 would love to have tags and folders(with permissions) as a feature.

[igamat]

Do we have any update on this ?

[bronz3beard]

For API usage, a work around I use is to group the dashboards by the slug attribute. then I can link to embedded dashboards via a specific topic.

For example - dashboard sales, KPI, expenses, has a slug of finance