Feature Request: "labels" like Notion tags
complete
M
Michael Bräutigam
"labels" which only live within an object property (similar to Notion tags).
Log In
Beth
complete
Labels are part of the latest release, you can read about it here: https://capacities.io/whats-new/release-52
Beth
Merged in a post:
Simple Select options with Text or Number type
R
Ralph Ngo
Current single select and multi-select have Tags as the values. This is overkill for something that doesn't need to have a dedicated content type
J
Joao Jesus
This is a "must need feature". Let me give an example: imagine that I want to create a property named "Priority", with just the options: "Urgent", "Normal" and "Low". I don't want this to be "tags" (as tags will appear on the graph, and I don't want this kind of information to be part of the graph). My suggestion is the creation of a new property type called "Single Select", that can act as a normal combo box with options.
M
Michael von Hohnhorst
Merged in a post:
Label property: Dropdown text selection
P
Pradip BABOU
I was using tag for book or people for status or categories (reading, finished reading, etc.) but I think it crowds the graph view with not relevant information. I instead made a text block so that I can still see the status but it doesn't show in the graph view.
It would be really nice to have a dropdown menu that we could feel with text options and just select one of them (or even many if we want to keep the Tag structure)
G
Gill McCowen
Agree - See also my comment here - https://capacities.io/feedback/p/label-property-dropdown-text-selection
G
Gill McCowen
I think this is an important requirement too, even though it is possible (with paid plan) to define a fixed tag set. However it still creates unnecessary tags which will eventually become unmanageable. For example I often want options such as yes/no/maybe, or simply options I have no need for outside the current table. Tags such as this also distort the graph view.
I could of course use a text field but want consistency of data to ensure accurate sorting/filtering, which can often go awry if a text field is used, and a small error is made in data entry.
Ideally I would like to see the following - the current properties 'select and multi-select' to be re-named to 'tag and multi-tag' (so that existing properties would continue to work) and new properties 'text select' and 'text multi-select' be introduced which are relevant only to that particular table/database.
P.S. I think this issue is being requested in several other places but under different descriptions such as drop down menu. select/multi-select etc. So I think it has more votes overall than indicated here...
G
Gill McCowen
Agree - options such as yes/no/maybe do not need to be tags and simply clutter up the list, yet are often required for consistency of data input to allow filter/sort
See also my comment here - https://capacities.io/feedback/p/label-property-dropdown-text-selection
S
Scoti Dodson
I'd love two versions of this: a single and multi select, similar to how those fields work in notion. I'd love for them to be tags, I just want to be able to define which tags are options for a given property.
M
Michael von Hohnhorst
Scoti Dodson: You can do that already by defining a fixed set (single and multi select are supported as well).
S
Scoti Dodson
Michael von Hohnhorst thanks! somehow missed that at the bottom
L
Liam Antony
Not having labels renders a number of fields somewhat useless. For example, project status. Tags don’t work as well
M
Michael von Hohnhorst
Merged in a post:
Dropdown menu
J
Jayakrishna Sai Kadali
It would be great if we could get dropdown menu for property section or at least have it as a property type
Load More
→