I caught onto it, but really only because I was tuned into other, different limitations on the Board view. I’m currently trying to get something working for a broader set of our organization to leverage Fibery, where many users don’t have data modeling experience to think about. While I quickly caught onto it being a limitation, I did try a number of different work arounds with auto linking and various things. Ultimately, there doesn’t appear to be a reasonable work around, so I wasted my time looking into it.
Yeah, think about Dynalist, Workflowy, Roam, etc. The power for them, and really Fibery/Notion/Coda as well, is to have the ability to show something in multiple contexts/views. I feel like in practice if I’m having to constantly fuss with data models to make sure they support a certain view I care about, it just isn’t going to be super useful in practice if I can’t trust it is going to work for a given use case I come up with.
However, in this case the “Issue Type” isn’t even really like a child to parent relationship. It is just a common set of types that all of the parents leverage. This is why I think the toy data example is probably not helping here.
I agree it is reasonable to argue to keep it simple, but it is common with tools like Airtable and Notion to start with a single select field and later convert to a Type/Table down the road. That would actually limit you on the views you can utilize in Notion, which is, along with JIRA integration, pretty much why I am here.
The argument for using a type instead of single select is just it is often helpful with teams so that you can include a description so that people know what you mean by Priority or Status. For example, what deserves to be a High vs Highest priority or when do you use a Status of Open vs To Do. You could add a rich text field where you discuss this further.
The real reason I bring it up is it is exactly the issue that I was currently fighting with, when trying to get some smart folders setup for JIRA projects. The JIRA integration seemed to require me to import it as a type, but found it is kind of broken.