Skip to main content
Open

custom field manager and robust application of tags/metadata

Related products:Mapping & Diagramming
Kyle Chipman
Robert Johnson
mlanders
Kiron Bondale
Alan Heckman
+68
  • Kyle Chipman
    Kyle Chipman
  • Robert Johnson
    Robert Johnson
  • mlanders
    mlanders
  • Kiron Bondale
    Kiron Bondale
  • Alan Heckman
    Alan Heckman
  • adamdunford
  • Adam Karminski
    Adam Karminski
  • Staus
  • Peter Green
    Peter Green
  • J Cornelius
  • Preben T. A. Arentoft
    Preben T. A. Arentoft
  • Sahan H
  • Gav
  • Nathan Jones
  • Sandra Uptas
  • Jonas
  • Karl Mochel
  • StephB
  • Rrr
  • Lee Watterworth
  • Kathleen Castro
  • Josh Phillips
  • Alex Hoffman
  • Greyson
  • pedro segreto
    pedro segreto
  • Anna Campbell
    Anna Campbell
  • James Wilson
    James Wilson
  • Dennis Lees
  • Marina Alvarez
  • Rebecca Haley
  • Fabio Chavasco
  • NathanB
  • Carlos Diosdado
  • Sam Gerace
  • Thomas Hogan
  • Linus Hallberg
  • Joanna Kleinschmidt
  • Mak Kordic
  • Brett von Halle
  • Sabira Lakhani
  • BarryH
  • Cate Amery
    Cate Amery
  • chrisdawson
  • knamaky
  • Lauree Schloss
    Lauree Schloss
  • Jun Chan
  • Daniel Castro
  • Soumyadeep Mandal
    Soumyadeep Mandal
  • Anton Antonov
  • JamesD
  • Kivi Shapiro
  • WolfgangRathert
    WolfgangRathert
  • Felix Boudreault
  • Mark Hanney
  • Gabriele Malaspina
  • Crisper
  • Petr Leitermann
  • Jesse Cruce
  • Paula Schwabe
  • HayleyBone
  • Alex Canning
  • Wubbel
  • mattmatt
  • Taylor Wright
    Taylor Wright
  • Tadashi Ushiroda
  • Naureka
  • Kelsey Comstock
  • LauraF
  • Juca Tornovsky
  • Dan Defenbaugh
  • Kelly Berryman
  • Mads Pålsrud
  • Marcos Pereira

maybe build on the table tool, but create a special “metadata” version that’s dedicated to managing a common data structure across any/all elements contained within that board, project, or workspace. different tabs for different metadata/tag/custom field sets.

the table would have all the database like features:

  • link/relate/associate elements
  • rollup/lookup within board/space 
  • formula type custom field 
  • conditional rules 
  • filtering/sorting

then each board element that inherits that structure appears in the table as a record with an id and internal wiki-style link. the conditional rules and formulas could determine what auto-tags are applied (or styling or relationship types) for particular shapes, tools, or lines in different contexts. and imagine setting relationship rules:

all of these lines indicate X and all those lines indicate Y; when you connect card A types to card B types with line-type X, you get [insert whatever result you want]; but if you use line-type Y, you get [insert another result] instead.

Was it helpful?

2 replies

Eca
Mironeer
Forum|alt.badge.img+2
  • Mironeer
  • 2053 replies
  • March 15, 2025

HI ​@mog grob,

Thanks so much for taking the time to submit this idea. Our team will review this and it’s open for votes and comments. 

 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!

 

Thank you again for helping make Miro better!


  • Author
  • Beginner
  • 2 replies
  • March 20, 2025

I wonder whether current miro users would see the value in something like this (what do I know?); might be more of a market-expansion thing.


Reply