Open unusualevent opened 2 months ago
Could you give an example why you need to regularly add tags. This could probably be restructured to prevent this problem from occurring.
e.g. just after a day of using it, I have all-new tags.
so, the target audience for this bug would be "new/fresh users of the software"
could you give an example? normally you timespans with multiple tags on it, so adding all tags to a dashboard entity seems like misuse.
normally you what?? building dashboards isn't illustrated anywhere as a best practice.
I was trying to reproduce the dash shown in screenshots.
hmmm, it's possible that you expect people to make dashboards of "type:{a}" where each line is the thing, instead of "{any tag}:{anything}"
that doesn't seem very clear up front.
e.g., I was making tags like:
"project-a:{subcomponent}" "project-b:{subcomponent}"
if the dashboards are limited to only being able to interpret one prefix at a time, that changes how you'd make tags and how you'd make dashboards.
I think it's also that, given that limitation, I have no idea what the core tag prefixes would end up being.
You could do it like this:
project:a subcomponent:one
project:b subcomponent:one
project:a subcomponent:two
Each line would be different time span.
Is your feature request related to a problem? Please describe. If I start out with 5 tags, and make a dashboard, then later add 2 tags, you'd need to add those tags to the dashboard.
Describe the solution you'd like It would be nice to have a way to specify "all tags". e.g. @ everything,
*
or something else.Describe alternatives you've considered It might be possible to, /by hand/, list all tags in one tab and add them to /every/ dashboard widget (which gets larger the more widgets you have and the more tags you have)
Additional context I think this project is cool. Is that additional context? 😅