Labels/Tags for Entities

[gregbacchus]

I love the way labels are used in github/gitlab.

It would be great to have a label field type in Fibery with the ability to manage colors etc for the labels applied.

Then, of course, it would be necessary to be able to search and filter by applied labels. Even a cross-entity label search/filter/board might be good.

[AnadinX]

Nice yeah. Perhaps even as an entitiy. I for instance might use them as ‘Themes’ and have them apply to Epics/Stories/Tasks etc. ?

[Shafqat_Ullah]

This is basically, Tagging, as it exists in TP.

Tagging is definitely a very useful feature and need not be a type itself. Tags can be attached to entities of any type.

[Pagandai_V_Pannirsel]

How to make key word tag in wiki , so that one can find it in wiki docs quickely via search if possible of any item in tables of any etentity .Can field be used as tag or not

[B_Sp]

I have actually been wondering about this with some challenges I’m trying to figure out organizing Fibery connected with entities having various containers. I just posted about the ability for entities to have multiple types associated as a way to solve this potentially, although this may be something that is fundamentally against the basic framework of Fibery.

Entities able to belong to multiple types

Hi, I know I’ve discussed this with you guys directly, but it’s such a big point for me I wanted to post here as a separate feature request, I hope this is a good place for this comment. I have multiple instances where I am seeing the need to have entities in a few places in Fibery, most readily with multiple types applied. Here are some examples: Idea entity. This is an item of any sort my team will quickly put into Fibery, such as “let’s explore partnership x,” “Run through of server set-u…

I have found most implementations of tags wanting, so if you guys do go down the road and relase Tags, I really hope they will be as well thought out as the rest of your app - things like hierarchy, some good tie in to Types, and so on.

[paul.a.matheson]

I don’t see it as tagging.

Say for instance an entity has 10 or so fields related to a specific category. The entity panel can get super bloated if you just have a running list of all the fields. They should be able to be grouped in different ways.. In the same way you can drag or hide fields from an entity view, you should be able to drag line breaks and headers to section things off.

Being able to add columns is nice but headers would be even better.

[RonMakesSystems]

Hi Paul,

I think what you are describing sounds more similar to field grouping than tagging. These are open ideas about it:

Declutter the entity display by grouping fields in collapsible field groups

Declutter the entity display by grouping fields in collapsible field groups. Currently the fields, especially many to many relation fields which cannot be hidden, are taking up a lot of space and is a big UX tension. In general, I see that users (including myself) work mostly with title and richt text content of entities. Although Fibery apears more structure oriented, day to day work with Fibery requires a lot of clicks and the fields are a big distraction. Drupal solved this also with the f…

Group fields in Table View as columns (and maybe other places)

When working with larger databases, tables can quickly grow to many dozens of fields, which makes navigation across columns harder. Currently it is possible to hide columns individually, but in practice many fields belong to logical groups (for example planning fields, metrics, metadata, etc.). Suggestion: Allow creating column groups inside table views. For example: Planning • Start Date • End Date • Owner Metrics • Budget • Revenue • Conversion Rate Metadata • Created By • Creat…

Frontend is essential!

Having a lot of fields visible and then managing work around them can feel overwhelming. To ease this it would be very handy to organize sets of fields into named areas/sections. Certainly, I’d like to be able to name and re-arrange those sections as well.

In general, I think Labels/Tags are solvable today with Single or Multi selects. Or to-one or to-many relationships. But I might be mistaken, as I don’t know the date of Fibery well enough when this post was created to know what was changed since.