Item metadata (like in Jira) - need community input please!
We launched @Atono a while back and we're now building out a series of features to enable Jira users to bring their old data with them. Our Linear import was pretty simple but Jira is a whole'nother ball of string.
Context: Atono is intended to be opinionated, intuitive and go further than Jira. Think Jira + flagsmith + amplitude in one product for cross functional teams to get a job done without complexity.
Jira uses the traditional concept of "Epics" but also has "Tasks, Products, Story, Feature and Request" for item types. Atono has a concept of a "Story" and "Bug" (others to come) and uses Product Theme to group stories into themes. Is a "theme" expansive enough to cover these other item types in your environment or do you need "Epics" and others?
Jira allows users to add labels ad-hoc, for any purpose. So each workspace is a unique creation. Should labels be allowed in a clean layout of stories and bugs?
Jira allows for custom fields, for any purpose. Complicated to manage, keep from proliferating, they become validation checks to restrict state change, etc. Often these are used to mask poor process, workflow, reporting needs, system limitations, etc. Should we allow any and all custom fields, some, none, etc?
Thank you for reading this - advice is welcomed!!
Replies
Really appreciate the transparency around these trade-offs, Jira’s legacy complexity can be a beast to tame. I’d say themes can absolutely cover a lot if they're paired with smart filtering and tagging logic.
As for labels and custom fields: minimalism wins until user scale demands flexibility. Maybe a progressive system where fields unlock based on workflow needs instead of dumping it all up front?
Atono
@vivek_sharma_25 Interesting idea Vivek thank you for sharing that. I think we've layered in a smart implementation of filtering which seems to work well for users (save filters, share them, use on dashboard, etc.). I want to give the progressive unlock some additional thought!